From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>, Alan Cox <alan@redhat.com>,
Jens Axboe <axboe@suse.de>
Subject: Re: Linux v2.5.42
Date: Sat, 12 Oct 2002 14:43:22 +0100 [thread overview]
Message-ID: <20021012144322.A17332@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0210112134160.7166-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Fri, Oct 11, 2002 at 09:59:58PM -0700
On Fri, Oct 11, 2002 at 09:59:58PM -0700, Linus Torvalds wrote:
>
> Augh.. People have been mailbombing me apparently because a lot of people
> finally decided that they really want to sync with me due to the upcoming
> feature freeze, so there's a _lot_ of stuff here, all over the map.
BTW, there's another infrastructure feature I forgot when you asked
what should go in before feature freeze. And IMHO it's very important
(so why did I forget it..): IBM's read copy update synchronisation
primitives. They've shown significant improvements when used for the
file tables, dcache and routing cache, it has been around since before
2.5 forked, SuSE has it in their production kernel for a while, too and
akpm has it in his tree for while.
Even if those existing users don't get in yet I don't want to miss the
infrastructure in the 2.6 series.
next prev parent reply other threads:[~2002-10-12 13:37 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 4:59 Linus Torvalds
2002-10-12 5:53 ` Adrian Bunk
2002-10-12 7:23 ` Adrian Bunk
2002-10-12 7:52 ` Andres Salomon
2002-10-12 9:23 ` David S. Miller
2002-10-12 9:11 ` Adrian Bunk
2002-10-12 9:24 ` Adrian Bunk
2002-10-12 9:41 ` Sam Ravnborg
2002-10-12 10:21 ` Adrian Bunk
2002-10-12 9:50 ` Matthias Andree
2002-10-12 11:11 ` jw schultz
2002-10-12 11:29 ` Andres Salomon
2002-10-12 11:46 ` Alan Cox
2002-10-12 11:40 ` jw schultz
2002-10-12 17:47 ` Jon Portnoy
2002-10-12 18:10 ` Rik van Riel
2002-10-13 11:58 ` venom
2002-10-13 12:52 ` Michael Clark
2002-10-12 12:37 ` Ed Tomlinson
2002-10-12 13:32 ` Christoph Hellwig
2002-10-12 19:39 ` Andres Salomon
2002-10-12 13:43 ` Christoph Hellwig [this message]
2002-10-13 17:10 ` Dipankar Sarma
2002-10-14 10:01 ` Joe Thornber
2002-10-14 19:21 ` Christoph Hellwig
2002-10-14 19:32 ` Alexander Viro
2002-10-14 22:28 ` Joe Thornber
2002-10-12 17:14 Mark Peloquin
2002-10-12 19:34 ` Alan Cox
2002-10-12 19:37 ` jbradford
2002-10-13 23:55 ` Rob Landley
2002-10-13 12:41 ` [Evms-devel] " Michael Clark
2002-10-13 13:49 ` Christoph Hellwig
2002-10-13 15:16 ` Michael Clark
2002-10-13 15:35 ` Christoph Hellwig
2002-10-13 16:11 ` Brian Jackson
2002-10-13 16:26 ` Arjan van de Ven
2002-10-13 17:06 ` Brian Jackson
2002-10-13 19:58 ` Mark Hahn
2002-10-13 19:57 ` Rik van Riel
2002-10-13 20:26 ` Sean Neakums
2002-10-24 11:45 ` Alexander Kellett
2002-10-13 19:59 ` Andrew Morton
2002-10-13 20:24 ` Bernd Eckenfels
2002-10-14 15:11 ` Christoph Hellwig
2002-10-14 22:27 ` Bernd Eckenfels
2002-10-13 17:46 ` Robert Love
2002-10-13 18:34 ` Brian Jackson
2002-10-14 14:45 ` Christoph Hellwig
2002-10-13 13:41 ` Christoph Hellwig
2002-10-12 20:20 Dieter Nützel
2002-10-12 22:19 ` Hans Reiser
2002-10-14 17:37 Ben Rafanello
2002-10-15 2:47 Paul McKenney
2002-10-15 17:43 Mark Peloquin
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=20021012144322.A17332@infradead.org \
--to=hch@infradead.org \
--cc=alan@redhat.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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®