<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Original was more general pthread vs. userthread and I thought pthread_getspecific was also indicted.<br><br> - Jay<br><br><br>> From: dragisha@m3w.org<br>> To: jay.krell@cornell.edu<br>> Date: Mon, 29 Mar 2010 11:38:18 +0200<br>> CC: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] userthreads vs. pthreads performance?<br>> <br>> I can be wrong, but what FUTEX operations on Linux can have with<br>> pthread_getspecific?<br>> <br>> Operations are made on FUTEX, we know which and where, no need to ask<br>> for pthread_getspecific.<br>> <br>> Are we still talking about poor lock_mutex performance?<br>> <br>> <br>> On Mon, 2010-03-29 at 08:24 +0000, Jay K wrote:<br>> > Once you do throw in -fPIC and -shared, I have found __thread to be<br>> > significantly slower on Solaris/sparc and Linux/powerpc32, slower or<br>> > a wash on Linux/amd64, and twice as fast as pthread_getspecific on<br>> > Linux/x86.<br>> > I doesn't appear supported at all on Darwin, though<br>> > pthread_getspecific are very fast there (albeit not inlined).<br>> > I didn't test *BSD.<br>> -- <br>> Dragiša Durić <dragisha@m3w.org><br>> <br> </body>
</html>