From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Samuel Thibault <samuel.thibault@labri.fr>,
linux-kernel@vger.kernel.org, libc-hacker@sources.redhat.com,
libc-alpha@sources.redhat.com
Subject: Re: [ANN] Userspace M-on-N threading model implementation. Alpha release.
Date: Tue, 30 Jan 2007 12:53:16 +0300 [thread overview]
Message-ID: <20070130095316.GD2455@2ka.mipt.ru> (raw)
In-Reply-To: <20070130011817.GI3541@interface.residence.ens-lyon.fr>
On Tue, Jan 30, 2007 at 02:18:17AM +0100, Samuel Thibault (samuel.thibault@labri.fr) wrote:
> Hi,
>
> Evgenity, le Mon 29 Jan 2007 16:47:36 +0100, a écrit :
> > Userspace M-on-N threading model is based on the idea, that when signal
> > is delivered, kernel saves all information related to previous context
> > in stack, so it is possible to find it and replace.
>
> You may want to have a look at some existing implementations:
I saw most of them.
As far as I recall, only PTL (is not shown here) has preemptible
scheduler. NTL has it too, but is based on different approach.
> - Good old `FSU Pthreads' http://moss.csc.ncsu.edu/~mueller/pthreads/
> - fully POSIX-compliant `GnuPth' http://www.gnu.org/software/pth/
> - server-targetted `Capriccio'
> www.cs.berkeley.edu/~jcondit/capriccio-sosp-2003.pdf
> - efficient `ELiTE/Erlangen'
> http://www4.informatik.uni-erlangen.de/Projects/FORTWIHR/ELiTE/
> - and our portable, flexible, efficient `Marcel'
> http://runtime.futurs.inria.fr/marcel/
>
> Samuel
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-01-30 9:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40f323d00701290747y68c8e27ege824694bfa378f58@mail.gmail.com>
2007-01-29 14:52 ` [ANN] Userspace M-on-N threading model implementation. Alpha release Evgeniy Polyakov
2007-01-29 14:57 ` Evgeniy Polyakov
2007-01-29 16:40 ` Chris Friesen
2007-01-30 9:46 ` Evgeniy Polyakov
2007-01-30 1:18 ` Samuel Thibault
2007-01-30 9:53 ` Evgeniy Polyakov [this message]
2007-01-30 10:24 ` Samuel Thibault
2007-01-30 10:43 ` Evgeniy Polyakov
2007-02-01 4:28 ` Lee Revell
2007-02-01 7:09 ` Evgeniy Polyakov
2007-01-30 21:16 Kaz Kylheku
2007-01-31 8:47 ` Evgeniy Polyakov
2007-02-02 16:12 ` Bill Davidsen
2007-02-03 15:26 ` Arjan van de Ven
2007-02-04 20:12 ` Bill Davidsen
2007-02-04 20:20 ` Jakub Jelinek
2007-02-04 21:42 ` Bill Davidsen
2007-02-05 6:14 ` Arjan van de Ven
2007-02-14 12:17 ` Pavel Machek
2007-02-04 22:52 ` Davide Libenzi
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=20070130095316.GD2455@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=libc-alpha@sources.redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@labri.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.