All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@gmail.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Important for fs devs: rcu-walk merged upstream
Date: Sat, 8 Jan 2011 13:54:47 +1100	[thread overview]
Message-ID: <AANLkTimBrR1LkVHOxZA=UUmKsnxfsFLr9z_AhXUHQ_7N@mail.gmail.com> (raw)

The vfs-scale branch is now upstream. If you haven't
looked yet, your filesystem is likely to have been
touched, so check it out.

Also look at Documentation/filesystems/porting and
path-lookup.txt.

The dcache_lock stuff should have been all done for you
(for in-tree filesystems, I can help out of tree fses with
conversions there if you ping me offline).

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.

Out of tree filesystems: you _have_ to at least add a line
of code to the above functions in order to specify that
you don't want to participate in rcu-walk.

Otherwise, you don't have to care about rcu-walk if you
have a legacy or special filesystem like configfs then I'd
advise against anything fancy. But if you have a
userbase and you expect them to actually do any path
lookups into your filesystem, please take a look.

This is a big and complex change by any measure, so
please don't be afraid to ask for help or clarification. I'd
also really like to be able to update documentation
based on questions from fs maintainers (in and out of
tree) who are trying to follow it and bring their code up to
speed.

Thanks,
Nick

             reply	other threads:[~2011-01-08  2:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08  2:54 Nick Piggin [this message]
2011-01-08  9:10 ` Important for fs devs: rcu-walk merged upstream 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
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='AANLkTimBrR1LkVHOxZA=UUmKsnxfsFLr9z_AhXUHQ_7N@mail.gmail.com' \
    --to=npiggin@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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.