I implemented the timeout feature for all of the platforms, which
included both lutexes and futexes. IIRC, this covered three
multi-threading build+platform options: futexes on linux, lutexes on
linux, and lutexes on darwin. I wasn't able to test the lutex on
darwin case, but I think the "lutex on linux" case could reasonably
suffice for that test.
On linux, you can achieve the lutex vs. futex option by pushing
sb-lutex onto the features list when you compile SBCL.
Revisions from the pdf on page 18:
"dicated" should be "predicated"
"viously failed" should be "previously failed"
Perhaps you already have the experience and permissions to make these
changes, but before you update the patch, I'd recommend you get buy-in
from someone that can review and submit such a patch to the trunk.
Personally, I'm putting off the updating of my patch until I need to
upgrade the version of SBCL that I use. But, I'd be happy to update
it if said buy-in existed.
Please feel free to ask further questions, as I'm quite interested in
seeing the timeout feature added. At this point, I've wanted it for
over three years.
On Thu, Mar 4, 2010 at 1:35 PM, V. Glenn Tarcea <gtarcea@...> wrote:
> Hi Nathan,
> Thanks. What I was interpreting from the email exchange, perhaps
> incorrectly, was that a form of (F)utex had been extended to all the other
> platforms. That is there is a pthreads-futex.c file that in theory could be
> used on all the platforms that don't have native futex support. I took
> David's email to mean that something like this was implemented for the
> platforms that don't have native futexes.
> David: Is this the case, or did the extensions you are talking about apply
> just to platforms that have a form of native support?
> V. Glenn Tarcea
>> -----Original Message-----
>> From: Nathan Froyd [mailto:froydnj@...]
>> Sent: Thursday, March 04, 2010 2:15 PM
>> To: V. Glenn Tarcea
>> Cc: David L. Rager; sbcl-devel@...
>> Subject: Re: [Sbcl-devel] Question on Futex Comment (Another MacOSX
>> related item)
>> On Thu, Mar 4, 2010 at 2:08 PM, V. Glenn Tarcea <gtarcea@...> wrote:
>> > Does this mean that the (L)utex code goes away? On the Mac it is
>> > using (L)utexes as opposed to (F)utexes.
>> Futexes are a Linux-only feature. Other platforms use lutexes as a
>> poor man's replacement for futexes.