From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Thread and process dentifiers (CPU affinity, kill)
Date: Fri, 20 May 2005 18:13:48 +0000 (UTC) [thread overview]
Message-ID: <d6l9cs$l1t$1@news.cistron.nl> (raw)
In-Reply-To: <20050520165307.GG23488@csclub.uwaterloo.ca>
In article <20050520165307.GG23488@csclub.uwaterloo.ca>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca> wrote:
>On Fri, May 20, 2005 at 04:51:10PM +0200, Olivier Croquette wrote:
>> From the beginning we are talking about the present GNU/Linux systems,
>> which do already use NTPL in standard. NPTL is no future standard, it is
>> present standard.
>
>Hmm, I just noticed the page I found about NPTL had 2005 date one place
>and 2002 in another. Yeah that is what people are using already.
>
>Most current i386 systems do NOT use NPTL yet by default since it only
>works on 2.6 kernels, and even then probably only if glibc was compiled
>that way.
No. On modern systems, glibc contains both LinuxThreads and NPTL.
They have the same ABI. At runtime one of the two is selected,
depending on if the currently running kernel supports NTPL.
You can also force it by setting the LD_ASSUME_KERNEL environment
variable to 2.4 or 2.6.
Mike.
next prev parent reply other threads:[~2005-05-20 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 18:00 Olivier Croquette
2005-05-19 18:23 ` Lennart Sorensen
2005-05-19 19:46 ` Chris Friesen
2005-05-20 12:55 ` Lennart Sorensen
2005-05-20 14:51 ` Olivier Croquette
2005-05-20 16:53 ` Lennart Sorensen
2005-05-20 18:13 ` Miquel van Smoorenburg [this message]
2005-05-20 20:12 ` Lennart Sorensen
2005-05-23 12:56 ` Nix
2005-05-20 20:17 ` Olivier Croquette
2005-05-20 20:38 ` Lee Revell
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='d6l9cs$l1t$1@news.cistron.nl' \
--to=miquels@cistron.nl \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome