From: Marc-Christian Petersen <m.c.p@gmx.net>
To: Bill Abt <babt@us.ibm.com>,
pthreads-devel@www-124.southbury.usf.ibm.com,
pthreads-users@www-124.southbury.usf.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: NGPT 2.2.0 RELEASED: TOPS LINUXTHREADS AND NPTL IN SCALABILITY AND PERFORMANCE
Date: Sat, 11 Jan 2003 02:05:50 +0100 [thread overview]
Message-ID: <200301110203.09346.m.c.p@gmx.net> (raw)
In-Reply-To: <OFD6D876A7.7D7E3A46-ON85256CAA.0068C7D5@us.ibm.com>
On Friday 10 January 2003 20:58, Bill Abt wrote:
Hi Bill,
> In this release, the primary focus was performance. Significant
> performance and scalability enhance-
> ments have been made to this release making it the fastest and most
> scalable POSIX compliant
> threads package available on the Linux platform.
hmm, can this be true?
>From the website: http://www-124.ibm.com/developerworks/oss/pthreads/
"Linus Torvalds: Look at Next Generation POSIX Threads (NGPT) for the future"
"of threads, he advised. "pthreads are horrible, and Linux has a very"
"different model, and there was no glue between the two." NGPT could be that"
"glue."
_when_ did Linus say that? :)
> NGPT Release 2.2.0 is a point release of the "Next Generation" of Linux
> pthreads support.
> This release is fully suitable as a replacement for LinuxThreads by either a
> single user or group or and entire distribution.
so, KDE works now but instead you made mozilla, xmms and galeon gone to death
;)
ciao, Marc
next prev parent reply other threads:[~2003-01-11 0:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-01-11 6:47 Dan Kegel
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=200301110203.09346.m.c.p@gmx.net \
--to=m.c.p@gmx.net \
--cc=babt@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pthreads-devel@www-124.southbury.usf.ibm.com \
--cc=pthreads-users@www-124.southbury.usf.ibm.com \
/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.