public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: autofs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ian Kent <raven@themaw.net>
Subject: [PATCH 0/6] Teach autofs about RCU-walk
Date: Mon, 25 Aug 2014 08:42:35 +1000	[thread overview]
Message-ID: <20140824223628.16196.5795.stgit@notabene.brown> (raw)

Hi Andrew,
 this series teaches autofs about RCU-walk so that we don't drop
 straight into REF-walk when we hit an autofs directory, and so that
 we avoid spinlocks as much as possible when performing an RCU-walk.

 This is needed so that the benefits of the recent NFS support for
 RCU-walk are fully available when NFS filesystems are automounted.

 Patches have been carefully reviewed and tested both with test suites
 and in production - thanks a lot to Ian Kent for his support there.

 If they could be queued for 3.18, I would appreciate it.

Thanks,
NeilBrown

---

NeilBrown (6):
      autofs4: allow RCU-walk to walk through autofs4.
      autofs4: factor should_expire() out of autofs4_expire_indirect.
      autofs4: make "autofs4_can_expire" idempotent.
      autofs4: avoid taking fs_lock during rcu-walk
      autofs4: d_manage() should return -EISDIR when appropriate in rcu-walk mode.
      autofs: the documentation I wanted to read


 Documentation/filesystems/autofs4.txt |  520 +++++++++++++++++++++++++++++++++
 fs/autofs4/autofs_i.h                 |    6 
 fs/autofs4/dev-ioctl.c                |    2 
 fs/autofs4/expire.c                   |  210 ++++++++-----
 fs/autofs4/root.c                     |   62 +++-
 5 files changed, 698 insertions(+), 102 deletions(-)
 create mode 100644 Documentation/filesystems/autofs4.txt

-- 
Signature


             reply	other threads:[~2014-08-24 22:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24 22:42 NeilBrown [this message]
2014-08-24 22:42 ` [PATCH 3/6] autofs4: make "autofs4_can_expire" idempotent NeilBrown
2014-08-24 22:42 ` [PATCH 6/6] autofs: the documentation I wanted to read NeilBrown
2014-08-24 22:42 ` [PATCH 2/6] autofs4: factor should_expire() out of autofs4_expire_indirect NeilBrown
2014-08-24 22:42 ` [PATCH 5/6] autofs4: d_manage() should return -EISDIR when appropriate in rcu-walk mode NeilBrown
2014-08-24 22:42 ` [PATCH 4/6] autofs4: avoid taking fs_lock during rcu-walk NeilBrown
2014-08-24 22:42 ` [PATCH 1/6] autofs4: allow RCU-walk to walk through autofs4 NeilBrown

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=20140824223628.16196.5795.stgit@notabene.brown \
    --to=neilb@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=autofs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raven@themaw.net \
    /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