From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Christoph Hellwig <hch@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Rusty Russell <rusty@rustcorp.com.au>,
Ulrich Drepper <drepper@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] futex requeueing feature, futex-requeue-2.5.69-D3
Date: Tue, 20 May 2003 11:12:28 +0200 [thread overview]
Message-ID: <20030520111228.I626@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20030520075627.A28002@infradead.org>; from hch@infradead.org on Tue, May 20, 2003 at 07:56:27AM +0100
Hi,
On Tue, May 20, 2003 at 07:56:27AM +0100, Christoph Hellwig wrote:
> On Tue, May 20, 2003 at 08:27:03AM +0200, Ingo Molnar wrote:
> > yes, but the damage has been done already, and now we've got to start the
> > slow wait for the old syscall to flush out of our tree.
>
> Actually it should go away before 2.6.0. sys_futex never was part of a
> released stable kernel so having the old_ version around is silly. I
> Think it's enough time until 2.6 hits the roads for people to have those
> vendor libc flushed out that use it. (and sys_futex still isn't used
> in the glibc CVS, only in the addon nptl package with pre-1 release
> numbers.)
This sounds reasonable. The people who shipped that already to
customers have so heavily patched kernels, that this simple patch
for the old sys_futex shouldn't really matter.
But cluttering the kernel with an API/ABI that was born in the
same development cycle, where it has been obsoleted sounds not
worth the bytes it consumes. And so we have a syscall slot
available for the next development cycle.
Or did anybody promise that this was final already? Usally this
promise comes with x.even.y not with x.odd.y .
Regards
Ingo Oeser
next prev parent reply other threads:[~2003-05-20 11:57 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 9:31 Ingo Molnar
2003-05-19 10:10 ` Christoph Hellwig
2003-05-19 10:16 ` Ingo Molnar
2003-05-19 11:49 ` Christoph Hellwig
2003-05-19 12:33 ` [patch] futex API cleanups, futex-api-cleanup-2.5.69-A2 Ingo Molnar
2003-05-19 12:51 ` Ingo Molnar
2003-05-19 14:47 ` bert hubert
2003-05-19 16:02 ` Ingo Molnar
2003-05-19 15:18 ` Linus Torvalds
2003-05-19 16:06 ` Ingo Molnar
2003-05-19 23:33 ` Jamie Lokier
2003-05-20 0:39 ` Rusty Russell
2003-05-20 1:14 ` Davide Libenzi
2003-05-20 1:44 ` Jamie Lokier
2003-05-20 16:54 ` Davide Libenzi
2003-05-20 17:59 ` Jamie Lokier
2003-05-21 23:56 ` Davide Libenzi
2003-05-20 1:50 ` Jamie Lokier
2003-05-20 0:15 ` Rusty Russell
2003-05-20 0:08 ` [patch] futex requeueing feature, futex-requeue-2.5.69-D3 Rusty Russell
2003-05-20 0:31 ` Valdis.Kletnieks
2003-05-19 10:23 ` Andrew Morton
2003-05-19 10:30 ` [patch] futex requeueing feature, futex-requeue-2.5.69-D4 Ingo Molnar
2003-05-20 0:04 ` [patch] futex requeueing feature, futex-requeue-2.5.69-D3 Rusty Russell
2003-05-20 0:40 ` Ulrich Drepper
2003-05-20 1:46 ` Rusty Russell
2003-05-20 2:11 ` Ulrich Drepper
2003-05-20 6:27 ` Ingo Molnar
2003-05-20 6:56 ` Christoph Hellwig
2003-05-20 8:57 ` Rusty Russell
2003-05-20 9:03 ` Ingo Molnar
2003-05-20 9:51 ` Christoph Hellwig
2003-05-20 12:56 ` [patch] futex patches, futex-2.5.69-A2 Ingo Molnar
2003-05-20 14:08 ` Christoph Hellwig
2003-05-20 16:02 ` Ingo Molnar
2003-05-20 19:55 ` Christoph Hellwig
2003-05-21 5:06 ` Martin Schlemmer
2003-05-21 6:31 ` Christoph Hellwig
2003-05-20 15:46 ` [patch] futex requeueing feature, futex-requeue-2.5.69-D3 Linus Torvalds
2003-05-20 9:12 ` Ingo Oeser [this message]
2003-05-20 15:41 ` Linus Torvalds
2003-05-20 8:55 ` Rusty Russell
2003-05-20 6:19 ` Ingo Molnar
[not found] <3ECAC2AE.8090401@redhat.com>
2003-05-21 2:34 ` Rusty Russell
2003-05-21 9:48 ` Ingo Molnar
2003-05-21 10:24 ` Christoph Hellwig
2003-05-22 0:30 ` Rusty Russell
2003-05-22 9:15 ` Ingo Molnar
2003-05-22 10:35 ` Rusty Russell
2003-05-22 11:23 Martin Wirth
2003-05-22 11:34 ` Ingo Molnar
2003-05-22 12:04 ` William Lee Irwin III
[not found] <3ECCB319.4060706@dlr.de.suse.lists.linux.kernel>
2003-05-22 11:38 ` Andi Kleen
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=20030520111228.I626@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=drepper@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.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 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®