From: Eric Wong <normalperson@...>
Date: 2012-05-16T09:14:27+09:00
Subject: Re: How to ensure that a block runs entirely after other threads? (Thread.exclusive does not "work")

I単aki Baz Castillo <ibc@aliax.net> wrote:
> But thread t1 runs every 0.1 seconds so I've don't properly understood
> the doc about Thread.exclusive. So, is there any easy way for telling
> Ruby "run this block entirely without passing the GVL to other thread
> in the middle of the block"?

Thread.exclusive is code smell and a sign of improper (or lack of)
locking/synchronization in your code.  I don't think it's possible to
implement Thread.exclusive when using native threads, only with green
threads/fibers.