All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Tejun Heo <tj@kernel.org>, Eric Sandeen <sandeen@sandeen.net>,
	Fox Chen <foxhlchen@gmail.com>,
	Brice Goglin <brice.goglin@gmail.com>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Rick Lindsley <ricklind@linux.vnet.ibm.com>,
	David Howells <dhowells@redhat.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [REPOST PATCH v4 1/5] kernfs: move revalidate to be near lookup
Date: Fri, 04 Jun 2021 10:29:21 +0800	[thread overview]
Message-ID: <bcbb928cda44551c8587f4967289f4d060f03646.camel@themaw.net> (raw)
In-Reply-To: <87im2vq9xh.fsf@disp2133>

On Thu, 2021-06-03 at 09:50 -0500, Eric W. Biederman wrote:
> Ian Kent <raven@themaw.net> writes:
> 
> > While the dentry operation kernfs_dop_revalidate() is grouped with
> > dentry type functions it also has a strong affinity to the inode
> > operation ->lookup().
> > 
> > In order to take advantage of the VFS negative dentry caching that
> > can be used to reduce path lookup overhead on non-existent paths it
> > will need to call kernfs_find_ns(). So, to avoid a forward
> > declaration,
> > move it to be near kernfs_iop_lookup().
> > 
> > There's no functional change from this patch.
> 
> Does this patch compile independently?

Doubt it.

> 
> During the code movement  kernfs_active is replaced
> by kernfs_active_read which does not exist yet.

Oops, that was a consequence of reordering the series which I
didn't catch.

I'll fix that when I post a v5 which I'm going to have to do.

Thanks for looking at this Eric,
Ian
> 
> Eric
> 
> > Signed-off-by: Ian Kent <raven@themaw.net>
> > ---
> >  fs/kernfs/dir.c |   86 ++++++++++++++++++++++++++++---------------
> > ------------
> >  1 file changed, 43 insertions(+), 43 deletions(-)
> > 
> > diff --git a/fs/kernfs/dir.c b/fs/kernfs/dir.c
> > index 7e0e62deab53c..4c69e2af82dac 100644
> > --- a/fs/kernfs/dir.c
> > +++ b/fs/kernfs/dir.c
> > @@ -548,49 +548,6 @@ void kernfs_put(struct kernfs_node *kn)
> >  }
> >  EXPORT_SYMBOL_GPL(kernfs_put);
> >  
> > -static int kernfs_dop_revalidate(struct dentry *dentry, unsigned
> > int flags)
> > -{
> > -       struct kernfs_node *kn;
> > -
> > -       if (flags & LOOKUP_RCU)
> > -               return -ECHILD;
> > -
> > -       /* Always perform fresh lookup for negatives */
> > -       if (d_really_is_negative(dentry))
> > -               goto out_bad_unlocked;
> > -
> > -       kn = kernfs_dentry_node(dentry);
> > -       mutex_lock(&kernfs_mutex);
> > -
> > -       /* The kernfs node has been deactivated */
> > -       if (!kernfs_active(kn))
> > -               goto out_bad;
> > -
> > -       /* The kernfs node has been moved? */
> > -       if (kernfs_dentry_node(dentry->d_parent) != kn->parent)
> > -               goto out_bad;
> > -
> > -       /* The kernfs node has been renamed */
> > -       if (strcmp(dentry->d_name.name, kn->name) != 0)
> > -               goto out_bad;
> > -
> > -       /* The kernfs node has been moved to a different namespace
> > */
> > -       if (kn->parent && kernfs_ns_enabled(kn->parent) &&
> > -           kernfs_info(dentry->d_sb)->ns != kn->ns)
> > -               goto out_bad;
> > -
> > -       mutex_unlock(&kernfs_mutex);
> > -       return 1;
> > -out_bad:
> > -       mutex_unlock(&kernfs_mutex);
> > -out_bad_unlocked:
> > -       return 0;
> > -}
> > -
> > -const struct dentry_operations kernfs_dops = {
> > -       .d_revalidate   = kernfs_dop_revalidate,
> > -};
> > -
> >  /**
> >   * kernfs_node_from_dentry - determine kernfs_node associated with
> > a dentry
> >   * @dentry: the dentry in question
> > @@ -1073,6 +1030,49 @@ struct kernfs_node
> > *kernfs_create_empty_dir(struct kernfs_node *parent,
> >         return ERR_PTR(rc);
> >  }
> >  
> > +static int kernfs_dop_revalidate(struct dentry *dentry, unsigned
> > int flags)
> > +{
> > +       struct kernfs_node *kn;
> > +
> > +       if (flags & LOOKUP_RCU)
> > +               return -ECHILD;
> > +
> > +       /* Always perform fresh lookup for negatives */
> > +       if (d_really_is_negative(dentry))
> > +               goto out_bad_unlocked;
> > +
> > +       kn = kernfs_dentry_node(dentry);
> > +       mutex_lock(&kernfs_mutex);
> > +
> > +       /* The kernfs node has been deactivated */
> > +       if (!kernfs_active_read(kn))
> > +               goto out_bad;
> > +
> > +       /* The kernfs node has been moved? */
> > +       if (kernfs_dentry_node(dentry->d_parent) != kn->parent)
> > +               goto out_bad;
> > +
> > +       /* The kernfs node has been renamed */
> > +       if (strcmp(dentry->d_name.name, kn->name) != 0)
> > +               goto out_bad;
> > +
> > +       /* The kernfs node has been moved to a different namespace
> > */
> > +       if (kn->parent && kernfs_ns_enabled(kn->parent) &&
> > +           kernfs_info(dentry->d_sb)->ns != kn->ns)
> > +               goto out_bad;
> > +
> > +       mutex_unlock(&kernfs_mutex);
> > +       return 1;
> > +out_bad:
> > +       mutex_unlock(&kernfs_mutex);
> > +out_bad_unlocked:
> > +       return 0;
> > +}
> > +
> > +const struct dentry_operations kernfs_dops = {
> > +       .d_revalidate   = kernfs_dop_revalidate,
> > +};
> > +
> >  static struct dentry *kernfs_iop_lookup(struct inode *dir,
> >                                         struct dentry *dentry,
> >                                         unsigned int flags)



  reply	other threads:[~2021-06-04  2:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28  6:33 [REPOST PATCH v4 0/5] kernfs: proposed locking and concurrency improvement Ian Kent
2021-05-28  6:33 ` [REPOST PATCH v4 1/5] kernfs: move revalidate to be near lookup Ian Kent
2021-06-03 14:50   ` Eric W. Biederman
2021-06-04  2:29     ` Ian Kent [this message]
2021-05-28  6:34 ` [REPOST PATCH v4 2/5] kernfs: use VFS negative dentry caching Ian Kent
2021-06-01 12:41   ` Miklos Szeredi
2021-06-02  3:44     ` Ian Kent
2021-06-02  8:58       ` Miklos Szeredi
2021-06-02 10:57         ` Ian Kent
2021-06-03  2:15           ` Ian Kent
2021-06-03 23:57             ` Ian Kent
2021-06-04  1:07               ` Ian Kent
2021-06-03 17:26   ` Eric W. Biederman
2021-06-03 18:06     ` Miklos Szeredi
2021-06-03 22:02       ` Eric W. Biederman
2021-06-04  3:14         ` Ian Kent
2021-06-04 14:28           ` Eric W. Biederman
2021-06-05  3:19             ` Ian Kent
2021-06-05 20:52               ` Eric W. Biederman
2021-05-28  6:34 ` [REPOST PATCH v4 3/5] kernfs: switch kernfs to use an rwsem Ian Kent
2021-06-01 13:11   ` Miklos Szeredi
2021-06-03 16:59   ` Eric W. Biederman
2021-05-28  6:34 ` [REPOST PATCH v4 4/5] kernfs: use i_lock to protect concurrent inode updates Ian Kent
2021-05-31 14:53   ` [kernfs] 9a658329cd: stress-ng.get.ops_per_sec 191.4% improvement kernel test robot
2021-05-31 14:53     ` kernel test robot
2021-06-01 13:18   ` [REPOST PATCH v4 4/5] kernfs: use i_lock to protect concurrent inode updates Miklos Szeredi
2021-06-02  5:41     ` Ian Kent
2021-05-28  6:34 ` [REPOST PATCH v4 5/5] kernfs: add kernfs_need_inode_refresh() Ian Kent
2021-05-28  8:56 ` [REPOST PATCH v4 0/5] kernfs: proposed locking and concurrency improvement Greg Kroah-Hartman
2021-05-28 11:56   ` Fox Chen
2021-05-30  4:44   ` Fox Chen

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=bcbb928cda44551c8587f4967289f4d060f03646.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=brice.goglin@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=foxhlchen@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mtosatti@redhat.com \
    --cc=ricklind@linux.vnet.ibm.com \
    --cc=sandeen@sandeen.net \
    --cc=tj@kernel.org \
    --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 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.