From: Joel Becker <jlbec@evilplan.org>
To: Nick Piggin <npiggin@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Important for fs devs: rcu-walk merged upstream
Date: Mon, 10 Jan 2011 17:08:01 -0800 [thread overview]
Message-ID: <20110111010800.GE4879@mail.oracle.com> (raw)
In-Reply-To: <AANLkTimBrR1LkVHOxZA=UUmKsnxfsFLr9z_AhXUHQ_7N@mail.gmail.com>
On Sat, Jan 08, 2011 at 01:54:47PM +1100, Nick Piggin wrote:
> The rcu-walk stuff can be more tricky for your filesystem
> to take advantage of.
>
> If you supply a .d_revalidate, .permission, or .check_acl,
> then path walking is going to be slow and unscalable for
> you.
Do you mean "as slow and unscalable as it has always been" or
"even slower now"? A quick look suggests the former, but I wanted to be
sure.
Joel
--
"But all my words come back to me
In shades of mediocrity.
Like emptiness in harmony
I need someone to comfort me."
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2011-01-11 1:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 2:54 Important for fs devs: rcu-walk merged upstream Nick Piggin
2011-01-08 9:10 ` Marco Stornelli
2011-01-11 9:57 ` Nick Piggin
2011-01-11 9:57 ` Nick Piggin
2011-01-11 11:08 ` Miklos Szeredi
2011-01-10 14:38 ` J. R. Okajima
2011-01-11 12:57 ` Nick Piggin
2011-01-11 12:57 ` Nick Piggin
2011-01-11 1:08 ` Joel Becker [this message]
2011-01-11 13:06 ` Nick Piggin
2011-01-11 13:06 ` Nick Piggin
2011-01-13 14:58 ` Miklos Szeredi
2011-01-13 16:18 ` Miklos Szeredi
2011-01-14 1:21 ` Nick Piggin
2011-01-14 1:21 ` Nick Piggin
2011-01-14 8:45 ` Miklos Szeredi
2011-01-14 8:45 ` Miklos Szeredi
2011-01-14 8:52 ` Nick Piggin
2011-01-14 8:52 ` Nick Piggin
2011-01-14 9:38 ` Miklos Szeredi
2011-01-14 9:38 ` Miklos Szeredi
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=20110111010800.GE4879@mail.oracle.com \
--to=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.