From: Christoph Hellwig <hch@infradead.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Dave Chinner <david@fromorbit.com>,
linux-fsdevel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.35
Date: Mon, 2 Aug 2010 05:05:42 -0400 [thread overview]
Message-ID: <20100802090542.GA32322@infradead.org> (raw)
In-Reply-To: <20100802082428.GA23135@infradead.org>
On Mon, Aug 02, 2010 at 04:24:28AM -0400, Christoph Hellwig wrote:
> .36. I'd much rather see the inode_lock scaling or the lockless path
> walk going in before, but I haven't checked how complicated the
> reordering would be. The lockless path walk also is only rather
> theoretically useful until we do ACL checks lockless as we're having
> ACLs enabled pretty much everywhere at least in the distros.
>From a quick look it seems like the inode_lock splitup can easily
be moved forward, and it would help us with doing some work on the
writeback side. The problem is that it would need rebasing ontop
of both the vfs and writeback (aka block) trees.
next prev parent reply other threads:[~2010-08-02 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim8FALeVG+NPLNLEQChu=dPD=GHSpnxmZHYgsNx@mail.gmail.com>
[not found] ` <20100802023322.GA19164@dastard>
[not found] ` <AANLkTint_s6h_EC7mDiPsyxr=C0GSrnrgJYkCCU7JEtN@mail.gmail.com>
[not found] ` <20100802055834.GB19164@dastard>
2010-08-02 7:55 ` Linux 2.6.35 Nick Piggin
2010-08-02 8:24 ` Christoph Hellwig
2010-08-02 8:46 ` KOSAKI Motohiro
2010-08-02 9:05 ` Christoph Hellwig [this message]
2010-08-02 10:07 ` Nick Piggin
2010-08-02 9:51 ` Nick Piggin
[not found] ` <87tyncds89.fsf@basil.nowhere.org>
2010-08-03 9:28 ` Nick Piggin
2010-08-03 9:49 ` Andi Kleen
2010-08-03 15:05 ` Henrique de Moraes Holschuh
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=20100802090542.GA32322@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).