Re: System threads (pthreads)

Anyone?  I'm mainly wondering what were the difficulties people 
encountered in making ST interop with threads (why it's not just a 
matter of interrupting the blocking select() call).

A more intrusive (but potentially more efficient) way to implement 
interop with threads is to use pipes (requires modifying the reactor 
itself; done in Twisted) or use small timeouts on the select (done in 
libasync-smp).

Thanks, for any answers.


Yang Zhang wrote:
> Also, has interop with valgrind been fixed?
> 
> If not, does anybody understand precisely what the problems are with 
> pthreads and valgrind?
> 
> Thanks!
> 
> 
> Yang Zhang wrote:
>> Hi, I've only been able to dig up some old mailing list posts about 
>> system threads (pthreads) not being usable in a st-based program.  Has 
>> there been any progress on this front?
>>
>> One approach suggested by the FAQ is to adopt a multi-process 
>> approach, but IPC overhead (incl. shared memory) is substantial 
>> compared to threads, and the approach generally makes things more 
>> complex.
>>
>> (FWIW, in the past, I've added thread support to other async 
>> programming frameworks by creating a lightweight thread that listens 
>> on a socket for connections from other system threads.)
>>
>> Thanks in advance for any answers.
> 
> 


-- 
Yang Zhang
http://www.mit.edu/~y_z/

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone