linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Chengguang Xu <cgxu519@mykernel.net>,
	miklos@szeredi.hu, viro@zeniv.linux.org.uk, amir73il@gmail.com
Cc: linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org
Subject: Re: [RFC PATCH v3 0/9] Suppress negative dentry
Date: Mon, 18 May 2020 08:53:31 +0800	[thread overview]
Message-ID: <e994d56ff1357013a85bde7be2e901476f743b83.camel@themaw.net> (raw)
In-Reply-To: <20200515072047.31454-1-cgxu519@mykernel.net>

On Fri, 2020-05-15 at 15:20 +0800, Chengguang Xu wrote:
> This series adds a new lookup flag LOOKUP_DONTCACHE_NEGATIVE
> to indicate to drop negative dentry in slow path of lookup.
> 
> In overlayfs, negative dentries in upper/lower layers are useless
> after construction of overlayfs' own dentry, so in order to
> effectively reclaim those dentries, specify LOOKUP_DONTCACHE_NEGATIVE
> flag when doing lookup in upper/lower layers.

I've looked at this a couple of times now.

I'm not at all sure of the wisdom of adding a flag to a VFS function
that allows circumventing what a file system chooses to do.

I also do really see the need for it because only hashed negative
dentrys will be retained by the VFS so, if you see a hashed negative
dentry then you can cause it to be discarded on release of the last
reference by dropping it.

So what's different here, why is adding an argument to do that drop
in the VFS itself needed instead of just doing it in overlayfs?

> 
> Patch 1 adds flag LOOKUP_DONTCACHE_NEGATIVE and related logic in vfs
> layer.
> Patch 2 does lookup optimazation for overlayfs.
> Patch 3-9 just adjusts function argument when calling
> lookup_positive_unlocked() and lookup_one_len_unlocked().
> 
> v1->v2:
> - Only drop negative dentry in slow path of lookup.
> 
> v2->v3:
> - Drop negative dentry in vfs layer.
> - Rebase on latest linus-tree(5.7.0-rc5).
> 
> Chengguang Xu (9):
>   fs/dcache: Introduce a new lookup flag LOOKUP_DONTCACHE_NEGATIVE
>   ovl: Suppress negative dentry in lookup
>   cifs: Adjust argument for lookup_positive_unlocked()
>   debugfs: Adjust argument for lookup_positive_unlocked()
>   ecryptfs: Adjust argument for lookup_one_len_unlocked()
>   exportfs: Adjust argument for lookup_one_len_unlocked()
>   kernfs: Adjust argument for lookup_positive_unlocked()
>   nfsd: Adjust argument for lookup_positive_unlocked()
>   quota: Adjust argument for lookup_positive_unlocked()
> 
>  fs/cifs/cifsfs.c      |  2 +-
>  fs/debugfs/inode.c    |  2 +-
>  fs/ecryptfs/inode.c   |  2 +-
>  fs/exportfs/expfs.c   |  2 +-
>  fs/kernfs/mount.c     |  2 +-
>  fs/namei.c            | 14 ++++++++++----
>  fs/nfsd/nfs3xdr.c     |  2 +-
>  fs/nfsd/nfs4xdr.c     |  3 ++-
>  fs/overlayfs/namei.c  |  9 +++++----
>  fs/quota/dquot.c      |  3 ++-
>  include/linux/namei.h |  9 +++++++--
>  11 files changed, 32 insertions(+), 18 deletions(-)
> 


  parent reply	other threads:[~2020-05-18  0:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  7:20 [RFC PATCH v3 0/9] Suppress negative dentry Chengguang Xu
2020-05-15  7:20 ` [RFC PATCH v3 1/9] fs/dcache: Introduce a new lookup flag LOOKUP_DONTCACHE_NEGATIVE Chengguang Xu
2020-05-15  7:20 ` [RFC PATCH v3 2/9] ovl: Suppress negative dentry in lookup Chengguang Xu
2020-05-15  7:20 ` [RFC PATCH v3 3/9] cifs: Adjust argument for lookup_positive_unlocked() Chengguang Xu
2020-05-15  7:20 ` [RFC PATCH v3 4/9] debugfs: " Chengguang Xu
2020-05-15  7:20 ` [RFC PATCH v3 5/9] ecryptfs: Adjust argument for lookup_one_len_unlocked() Chengguang Xu
2020-05-15  7:20 ` [RFC PATCH v3 6/9] exportfs: " Chengguang Xu
2020-05-15  7:20 ` [RFC PATCH v3 7/9] kernfs: Adjust argument for lookup_positive_unlocked() Chengguang Xu
2020-05-15  7:20 ` [RFC PATCH v3 8/9] nfsd: " Chengguang Xu
2020-05-15  7:20 ` [RFC PATCH v3 9/9] quota: " Chengguang Xu
2020-05-15  7:30 ` [RFC PATCH v3 0/9] Suppress negative dentry Amir Goldstein
2020-05-15  8:25   ` Chengguang Xu
2020-05-15  8:42     ` Miklos Szeredi
2020-05-18  0:53 ` Ian Kent [this message]
2020-05-18  5:27   ` Amir Goldstein
2020-05-18  7:52     ` Miklos Szeredi
2020-05-18  8:51       ` Amir Goldstein
2020-05-18  9:17         ` Miklos Szeredi
2020-05-19  5:01       ` cgxu
2020-05-19  8:21         ` Miklos Szeredi
2020-05-19  9:23           ` cgxu
2020-05-20 14:44             ` Miklos Szeredi
2020-05-25 13:37               ` Chengguang Xu
2020-05-25 13:50                 ` Miklos Szeredi
2020-05-18 10:26     ` Ian Kent
2020-05-18 10:39       ` Ian Kent

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=e994d56ff1357013a85bde7be2e901476f743b83.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=amir73il@gmail.com \
    --cc=cgxu519@mykernel.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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).