From: Nick Piggin <npiggin@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Nick Piggin <npiggin@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: Linux 2.6.35
Date: Mon, 2 Aug 2010 18:14:22 +1000 [thread overview]
Message-ID: <20100802081422.GA8892@amd> (raw)
In-Reply-To: <20100802103204.3d1b2863.sfr@canb.auug.org.au>
On Mon, Aug 02, 2010 at 10:32:04AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Sun, 1 Aug 2010 16:52:42 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >
> > On a slightly happier note: one thing I do hope we can merge in the
> > upcoming merge window is Nick Piggin's cool VFS scalability series.
> > I've been using it on my own machine, and gone through all the commits
> > (not that I shouldn't go through some of them some more), and am
> > personally really excited about it. It's seldom we see major
> > performance improvements in core code that are quite that noticeable,
> > and Nick's whole RCU pathname lookup in particular just tickles me
> > pink.
>
> To that end, Nick, can you please submit that tree for inclusion in
> linux-next in case there are some interactions with some of the other
> stuff there? (or send it all to Al, instead (or both), I guess.)
Hi Stephen,
I will work something out with Al and try to have something in
linux-next ASAP.
next prev parent reply other threads:[~2010-08-02 8:14 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 23:52 Linux 2.6.35 Linus Torvalds
2010-08-02 0:32 ` Stephen Rothwell
2010-08-02 8:14 ` Nick Piggin [this message]
2010-08-02 8:52 ` Stephen Rothwell
2010-08-02 2:33 ` Dave Chinner
2010-08-02 2:50 ` Linus Torvalds
2010-08-02 5:58 ` Dave Chinner
2010-08-02 7:55 ` Nick Piggin
2010-08-02 8:24 ` Christoph Hellwig
2010-08-02 8:46 ` KOSAKI Motohiro
2010-08-02 9:05 ` Christoph Hellwig
2010-08-02 10:07 ` Nick Piggin
2010-08-02 9:51 ` Nick Piggin
2010-08-03 8:18 ` Andi Kleen
2010-08-03 9:28 ` Nick Piggin
2010-08-03 9:49 ` Andi Kleen
2010-08-03 15:05 ` Henrique de Moraes Holschuh
2010-08-02 8:51 ` make 3.82 fails on powerpc defconfig update [was: Linux 2.6.35] Thomas Backlund
2010-08-02 18:28 ` Sam Ravnborg
2010-08-02 20:46 ` Thomas Backlund
2010-08-02 20:51 ` Sam Ravnborg
2010-08-02 21:02 ` Andreas Schwab
2010-08-02 21:03 ` Thomas Backlund
2010-08-03 6:48 ` Sam Ravnborg
2010-08-07 17:56 ` Paul Smith
-- strict thread matches above, loose matches on Subject: below --
2010-08-02 2:31 Linux 2.6.35 Donald Parsons
2010-08-02 3:28 ` Randy Dunlap
2010-08-02 3:38 ` Bjorn Helgaas
2010-08-02 4:21 ` Donald Parsons
2010-08-02 13:48 ` Bjorn Helgaas
2010-08-02 15:59 ` Harald Hoyer
2010-08-02 22:09 ` Frédéric L. W. Meunier
2010-08-02 22:34 ` Frédéric L. W. Meunier
2010-08-02 18:38 ` Donald Parsons
2010-08-02 16:08 ` Harald Hoyer
2010-08-03 2:31 ` Donald Parsons
2010-08-03 4:42 ` Randy Dunlap
2010-08-03 10:24 ` Stefan Richter
2010-08-03 18:26 ` Donald Parsons
2010-08-03 16:26 ` Donald Parsons
2010-08-03 16:40 ` Randy Dunlap
2010-08-03 17:45 ` Donald Parsons
2010-08-03 18:35 ` Randy Dunlap
2010-08-03 22:34 ` Randy Dunlap
2010-08-04 20:15 ` 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=20100802081422.GA8892@amd \
--to=npiggin@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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