From: Dan Kegel <dank@kegel.com>
To: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: NGPT 2.2.0 RELEASED: TOPS LINUXTHREADS AND NPTL IN SCALABILITY AND PERFORMANCE
Date: Fri, 10 Jan 2003 22:47:20 -0800 [thread overview]
Message-ID: <3E1FBDF8.7000904@kegel.com> (raw)
Valdis.Kletnieks@vt.edu wrote:
> On Fri, 10 Jan 2003 20:33:46 EST, Jeff Garzik said:
>> On Fri, Jan 10, 2003 at 05:26:47PM -0800, jjs wrote:
>> > But according to my understanding, a more accurate
>> > measure of nptl performance would require a current
>> > glibc, with the nptl-specific enhancements -
>> >
>> > or am I missing something here?
>>
>> You are correct: you need a recent 2.5 kernel and a recent glibc.
>
> I'll bite - how recent a glibc? Does the 2.3.1 RPM that RedHat included
> on the Phoebe beta qualify, or do we need even more bleeding-edge?
https://listman.redhat.com/pipermail/phil-list/2003-January/000413.html
lists what sources are needed for the latest nptl.
Phoebe beta had a slightly earlier snapshot of nptl and glibc.
As far as the kernel goes, it's rumored
( https://listman.redhat.com/pipermail/phil-list/2003-January/000419.html )
that you're better off using a recent 2.5 kernel than the 2.4 backport
in phoebe.
I haven't tried NPTL myself, though, so what do I know...
- Dan
--
Dan Kegel
Linux User #78045
http://www.kegel.com
next reply other threads:[~2003-01-11 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 6:47 Dan Kegel [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-10 19:58 NGPT 2.2.0 RELEASED: TOPS LINUXTHREADS AND NPTL IN SCALABILITY AND PERFORMANCE Bill Abt
2003-01-11 1:05 ` Marc-Christian Petersen
2003-01-11 1:26 ` jjs
2003-01-11 1:33 ` Jeff Garzik
2003-01-11 1:41 ` Valdis.Kletnieks
2003-01-11 1:44 ` Jeff Garzik
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=3E1FBDF8.7000904@kegel.com \
--to=dank@kegel.com \
--cc=Valdis.Kletnieks@vt.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.