From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Nick Piggin <npiggin@kernel.dk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: rcu-walk and dcache scaling tree update and status
Date: Mon, 13 Dec 2010 14:40:49 +1100 [thread overview]
Message-ID: <20101213144049.fa3b14d9.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20101213023733.GB6522@amd>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
Hi Nick,
On Mon, 13 Dec 2010 13:37:33 +1100 Nick Piggin <npiggin@kernel.dk> wrote:
>
> Linus has suggested pretty strongly that he wants to pull this in the
> next merge window (recently, that "inodes will be RCU freed in 2.6.38"
> in an urelated discussion). As far as I know, that's what he's going to
> do. I'd like to get this some time in linux-next to improve test
> coverage (many filesystems I can't even test, so there are bound to be a
> few silly crashes). Stephen, how do I arrange that?
Well, you ask me :-) (letting me know where the git tree is).
I this case I would like an email from Al and/or Linus (and/or maybe
Christoph?) before I add this to linux-next as you say below that
(despite being as well tested as you can do) it does require more review
and buyin from others. Of course, if Linus is going to merge this during
the next merge window, then it really should be in linux-next as soon as
it is ready enough.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-12-13 3:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 2:37 Nick Piggin
2010-12-13 2:42 ` [patch] fs: scale vfsmount refcount (was Re: rcu-walk and dcache scaling tree update and status) Nick Piggin
2010-12-13 3:31 ` Nick Piggin
2010-12-13 3:43 ` Nick Piggin
2010-12-13 7:25 ` Eric Dumazet
2010-12-13 8:33 ` Nick Piggin
2010-12-14 12:40 ` Nick Piggin
2010-12-15 8:16 ` Andreas Dilger
2010-12-15 10:24 ` Nick Piggin
2010-12-13 2:53 ` rcu-walk and dcache scaling tree update and status Ed Tomlinson
2010-12-13 2:59 ` Nick Piggin
2010-12-13 3:45 ` Stephen Rothwell
2010-12-13 3:50 ` Nick Piggin
2010-12-13 3:40 ` Stephen Rothwell [this message]
2010-12-13 3:48 ` Nick Piggin
2010-12-14 0:03 ` Stephen Rothwell
2010-12-14 0:16 ` Stephen Rothwell
2010-12-13 16:48 Sedat Dilek
2010-12-13 23:21 ` Stephen Rothwell
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=20101213144049.fa3b14d9.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--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
all inboxes | Powered by JetHome®