mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Olivier Croquette <ocroquette@free.fr>
Cc: Miquel van Smoorenburg <miquels@cistron.nl>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Thread and process dentifiers (CPU affinity, kill)
Date: Fri, 20 May 2005 16:38:58 -0400	[thread overview]
Message-ID: <1116621539.29740.29.camel@mindpipe> (raw)
In-Reply-To: <428E45EA.3040603@free.fr>

On Fri, 2005-05-20 at 22:17 +0200, Olivier Croquette wrote:
> # export LD_ASSUME_KERNEL=2.4.1
> This is a clever way to enable some existing applications that rely on 
> LinuxThreads to continue to work in an NPTL environment, but is a 
> short-term solution. To make the most of the design and performance 
> benefits provided by NPTL, you should update the code for any existing 
> applications that use threading.

Applications that rely on linuxthreads, heh, that's a good one.

The most common use of LD_ASSUME_KERNEL is to force Linuxthreads to be
used in order to work around a bad bug in NPTL 0.60, often present on
Debian systems.  Ubuntu still reports NPTL 0.60, but they at least fixed
the bug for the Hoary release.  The Debian people refuse to.

The issue is very well known to JACK users.

Lee


      reply	other threads:[~2005-05-20 20:39 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
2005-05-23 12:56               ` Nix
2005-05-20 20:17             ` Olivier Croquette
2005-05-20 20:38               ` Lee Revell [this message]

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=1116621539.29740.29.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquels@cistron.nl \
    --cc=ocroquette@free.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 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®