From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Thread and process dentifiers (CPU affinity, kill)
Date: Fri, 20 May 2005 16:12:55 -0400 [thread overview]
Message-ID: <20050520201255.GG23621@csclub.uwaterloo.ca> (raw)
In-Reply-To: <d6l9cs$l1t$1@news.cistron.nl>
On Fri, May 20, 2005 at 06:13:48PM +0000, Miquel van Smoorenburg wrote:
> 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.
Well so far my tests show that glibc 2.3.2.ds1-21 on Debian Sarge when
running 2.6.11 kernel on i386 uses LinuxThreads, while on amd64 version
of Sarge it uses NPTL (and won't run with 2.4 kernel at all either).
Maybe Debian compiled their glibc to not do NPTL on i386 yet. Not sure.
Hmm, after checking, it turns out if you use errno in your program, it
drops to linuxthreads, while using #include <errno.h> makes it able to
use NPTL when using 2.6 kernel. Now my program works the same on i386
as on amd64 (I had to fix the errno to make it run on amd64 so that does
make some sense). Well I learned something new.
Len Sorensen
next prev parent reply other threads:[~2005-05-20 20: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
2005-05-20 20:12 ` Lennart Sorensen [this message]
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=20050520201255.GG23621@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
/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
all inboxes | Powered by JetHome®