From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org, cw@f00f.org
Subject: Re: Synchronization primitives in UML
Date: Tue, 09 Nov 2004 13:41:03 -0600 [thread overview]
Message-ID: <41911D4F.5080606@nortelnetworks.com> (raw)
In-Reply-To: <200411092015.10544.blaisorblade_spam@yahoo.it>
Blaisorblade wrote:
> Yes, I would like that, too, but futexes are 2.6 only, and probably also
> NPTL-only (we are going to fix that, at least for SKAS mode), but faster than
> anything else. Nothing apart this.
Actually, you can use raw futexes directly without needing any thread library.
There is even some helper code available if you search around a bit.
Chris
prev parent reply other threads:[~2004-11-09 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 19:36 Synchronization primitives in UML (was: Re: [uml-devel] Re: [patch 09/20] uml: use SIG_IGN for empty sighandler) Blaisorblade
2004-11-06 5:13 ` Jeff Dike
2004-11-09 17:44 ` Blaisorblade
2004-11-09 20:48 ` Jeff Dike
2004-11-09 19:15 ` Blaisorblade
2004-11-09 19:41 ` Chris Friesen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41911D4F.5080606@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=cw@f00f.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox