Re: [ANN] Userspace M-on-N threading model implementation. Alpha release.

On Tue, Jan 30, 2007 at 02:18:17AM +0100, Samuel Thibault (samuel.thibault@xxxxxxxx) 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: how do threads work?
    ... All of the the context switching is done in the kernel. ... All of the memory space is shared, including stack space, which means ...
    (comp.os.linux.development.system)
  • Re: [ANN] Userspace M-on-N threading model implementation. Alpha release.
    ... kernel saves all information related to previous context ... in stack, so it is possible to find it and replace. ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: Why cant we sleep in an ISR?
    ... interrupt is not associated with any context in the first place. ... includes the kernel and userspace stack pointers, the register set, ... this, an interrupt, depending on the version of your kernel and arch, ...
    (Linux-Kernel)
  • Re: Scheduling in interrupt and call trace
    ... the kernel to panic. ... seems that the stack trace is a kernel stack of process context since ... frame pointer when compiling the kernel, instead, I back traced by ...
    (Linux-Kernel)
  • [Full-disclosure] PHRACK 64: ATTACKING THE CORE
    ... - The Slab Allocator ... - Slab overflow exploiting: ... - Forcing a kernel path to sleep ... - Stack Frame Flow Recovery ...
    (Full-Disclosure)