From: Robert Love <rml@tech9.net>
To: Shawn <core@enodev.com>
Cc: Andrew Morton <akpm@digeo.com>,
Steven Cole <elenstev@mesatop.com>,
jeremy@goop.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: 2.5.64-mm6
Date: 13 Mar 2003 22:56:41 -0500 [thread overview]
Message-ID: <1047614200.1226.28.camel@icbm> (raw)
In-Reply-To: <1047613609.2848.3.camel@localhost.localdomain>
On Thu, 2003-03-13 at 22:46, Shawn wrote:
> This reminds me of something I've not looked into for some time.
>
> Being an active user of the 2.5 series including -mm, should I have
> updated glibc, or is there nothing new enough yet to warrant that?
In 2.3 and beyond (current is 2.3.2 I think), there are a few 2.5
changes. Nothing required, though.
The biggest is NPTL, which takes advantage of all the threading stuff.
There is also sysenter support.
And support for new 2.5 system calls - most, but not all, of them are
there. I know the affinity calls are. And the new posix_fadvise().
> Maybe I should just ask the glibc people. Wasn't sure what the proper
> forum was.
libc-alpha is the public glibc list. It is hosted at
sources.redhat.com.
Robert Love
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-03-14 3:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 11:26 2.5.64-mm6 Andrew Morton
2003-03-13 16:23 ` 2.5.64-mm6 Jeremy Fitzhardinge
2003-03-13 19:34 ` 2.5.64-mm6 Andrew Morton
2003-03-13 20:07 ` 2.5.64-mm6 Roger Larsson
2003-03-14 3:04 ` 2.5.64-mm6 Steven Cole
2003-03-14 3:28 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:46 ` 2.5.64-mm6 Shawn
2003-03-14 3:51 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:56 ` Robert Love [this message]
2003-03-13 20:35 ` 2.5.64-mm6 Thomas Molina
2003-03-14 9:29 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 11:55 ` 2.5.64-mm6 Andrew Morton
2003-03-15 8:38 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 12:01 ` 2.5.64-mm6 Helge Hafting
2003-03-14 12:14 ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:38 ` 2.5.64-mm6 Eli Carter
2003-03-14 20:53 ` 2.5.64-mm6 Andrew Morton
2003-03-14 22:01 ` 2.5.64-mm6 Eli Carter
2003-03-14 22:21 ` 2.5.64-mm6 Andrew Morton
2003-03-13 13:42 2.5.64-mm6 Felipe Alfaro Solana
2003-03-13 21:49 2.5.64-mm6 Felipe Alfaro Solana
2003-03-14 0:23 ` 2.5.64-mm6 Thomas Molina
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=1047614200.1226.28.camel@icbm \
--to=rml@tech9.net \
--cc=akpm@digeo.com \
--cc=core@enodev.com \
--cc=elenstev@mesatop.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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