Re: KSE, libpthread & libthr: almost newbie question
- From: Ruslan Ermilov <ru@xxxxxxxxxxx>
- Date: Fri, 27 Oct 2006 17:53:44 +0400
On Fri, Oct 27, 2006 at 02:43:21PM +0100, Nuno Antunes wrote:
On 10/27/06, Ruslan Ermilov <ru@xxxxxxxxxxx> wrote:It's still named libkse on sparc64 and sun4v.
KSE == N:M threading
A 1:1 threading (libthr) is much simpler than N:M threading (libpthread),
and thus doesn't require KSE support in the kernel; see kse(2) manpage
for details. Without the KSE option in the kernel, all kse(2) syscalls
will return EOPNOTSUPP, and a lot of code becomes redundant.
IIRC, I can even remember libpthread being originaly named libkse.
Cheers,
--
Ruslan Ermilov
ru@xxxxxxxxxxx
FreeBSD committer
Attachment:
pgpJGVKf3Wyn5.pgp
Description: PGP signature
- References:
- KSE, libpthread & libthr: almost newbie question
- From: Lev Serebryakov
- Re: KSE, libpthread & libthr: almost newbie question
- From: Ivan Voras
- Re: KSE, libpthread & libthr: almost newbie question
- From: Ruslan Ermilov
- Re: KSE, libpthread & libthr: almost newbie question
- From: Nuno Antunes
- KSE, libpthread & libthr: almost newbie question
- Prev by Date: Re: KSE, libpthread & libthr: almost newbie question
- Next by Date: Re: portupgrade not working for all ports
- Previous by thread: Re: KSE, libpthread & libthr: almost newbie question
- Next by thread: Re: KSE, libpthread & libthr: almost newbie question
- Index(es):
Relevant Pages
|
|