From: Nick Sieger Date: 2006-11-07T03:50:28+09:00 Subject: Re: fast mutexes for 1.8? ------=_Part_51846_5392420.1162839022715 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 11/6/06, Eric Hodel wrote: > > > > > I am slightly alarmed that this question is still open at this point. > > If YARV is moving Ruby from green threads to native threads, I would > > expect the important questions about what this will mean for > > synchronization (for both C-level extensions and Ruby) to have been > > resolved by now. Is there a global interpreter lock like Python? > > What > > is the migration path for people using Thread.critical? In what cases > > will C extensions have to change? > > > > Are answers to these questions known? > > Yes. Have you read Koichi's presentations? I believe most of the answers are in my notes from Ko1's talk at this year's RubyConf (see section titled "Threading"): http://blog.nicksieger.com/articles/2006/10/23/rubyconf-yarv-on-rails /Nick ------=_Part_51846_5392420.1162839022715 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 11/6/06, Eric Hodel <drbrain@segment7.net> wrote:
>
> I am slightly alarmed that this question is still open at this point.
> If YARV is moving Ruby from green threads to native threads, I would
> expect the important questions about what this will mean for
> synchronization (for both C-level extensions and Ruby) to have been
> resolved by now.  Is there a global interpreter lock like Python?
> What
> is the migration path for people using Thread.critical ?  In what cases
> will C extensions have to change?
>
> Are answers to these questions known?

Yes.  Have you read Koichi's presentations?

I believe most of the answers are in my notes from Ko1's talk at this year's RubyConf (see section titled "Threading"):

http://blog.nicksieger.com/articles/2006/10/23/rubyconf-yarv-on-rails

/Nick
------=_Part_51846_5392420.1162839022715--