From: Jonathan Corbet <corbet@lwn.net>
To: NeilBrown <neilb@suse.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: update path-lookup.md for parallel lookups
Date: Tue, 20 Nov 2018 09:38:25 -0700 [thread overview]
Message-ID: <20181120093825.7e009b1e@lwn.net> (raw)
In-Reply-To: <87k1l9dgx9.fsf@notabene.neil.brown.name>
On Mon, 19 Nov 2018 11:55:46 +1100
NeilBrown <neilb@suse.com> wrote:
> Since this document was written, i_mutex has been replace with
> i_rwsem, and shared locks are utilized to allow lookups in the one
> directory to happen in parallel.
>
> So replace i_mutex with i_rwsem, and explain how this is used for
> parallel lookups.
>
> Signed-off-by: NeilBrown <neilb@suse.com>
I've applied this, thanks. I do have a couple of small comments, though...
#1: what are the chances of getting this document converted to RST and
tied into our documentation tree?
#2: ...
> Just FYI
>
> $ git grep -w i_mutex | wc -l
> 262
>
> it was 276 before this patch... so a small improvement.
>
> NeilBrown
>
>
> Documentation/filesystems/path-lookup.md | 85 ++++++++++++++++++------
> 1 file changed, 66 insertions(+), 19 deletions(-)
>
> diff --git a/Documentation/filesystems/path-lookup.md b/Documentation/filesystems/path-lookup.md
> index e2edd45c4bc0..06151b178f80 100644
> --- a/Documentation/filesystems/path-lookup.md
> +++ b/Documentation/filesystems/path-lookup.md
> @@ -12,6 +12,10 @@ This write-up is based on three articles published at lwn.net:
> - <https://lwn.net/Articles/650786/> A walk among the symlinks
>
> Written by Neil Brown with help from Al Viro and Jon Corbet.
> +It has subsequently been updated to reflect changes in the kernel
> +including:
> +
> +- per-directory parallel name lookup.
I'm unconvinced about the value of putting changelogs into the docs
themselves; that's what we keep git around for. (I *do* think there's
some value of having something in a document giving a hint of how current
it is, though).
Thanks,
jon
prev parent reply other threads:[~2018-11-20 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 0:55 [PATCH] Documentation: update path-lookup.md for parallel lookups NeilBrown
2018-11-20 16:38 ` Jonathan Corbet [this message]
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=20181120093825.7e009b1e@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).