Pthread masters (that's you guy)

ruby-talk
1

i’m considering working on a binding to a library (drmaa) that, itself
requires/uses libpthread. what are the issues with using such a library from
a ruby built with/without pthred support?

if the c calls themselves manage the pthreads directly (which they do)
wouldn’t it be sufficient to simply protect access to these calls from more
than 1 ruby thread at a time?

-a

···

–

EMAIL :: Ara [dot] T [dot] Howard [at] noaa [dot] gov
PHONE :: 303.497.6469
ADDRESS :: E/GC2 325 Broadway, Boulder, CO 80305-3328
URL :: Solar-Terrestrial Physics Data | NCEI
TRY :: for l in ruby perl;do $l -e “print "\x3a\x2d\x29\x0a"”;done
===============================================================================

2

Hi,

···

In message “pthread masters (that’s you guy)” on 04/05/08, “Ara.T.Howard” Ara.T.Howard@noaa.gov writes:

if the c calls themselves manage the pthreads directly (which they do)
wouldn’t it be sufficient to simply protect access to these calls from more
than 1 ruby thread at a time?

Yes. I think you also need to protect vtalrm interrupt during
pthread-calling functions, wrapping with

TRAP_BEG;
function();
TRAP_END;

						matz.