All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benjamin Coddington" <bcodding@redhat.com>
To: "Trond Myklebust" <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/3] NFS: Fix a performance regression in readdir
Date: Wed, 30 Nov 2016 14:08:03 -0500	[thread overview]
Message-ID: <F7498BF3-4642-49F1-9283-7881FBE56E20@redhat.com> (raw)
In-Reply-To: <1479574497-38268-2-git-send-email-trond.myklebust@primarydata.com>

On 19 Nov 2016, at 11:54, Trond Myklebust wrote:

> Ben Coddington reports that commit 311324ad1713, by adding the 
> function
> nfs_dir_mapping_need_revalidate() that checks page cache validity on
> each call to nfs_readdir() causes a performance regression when
> the directory is being modified.
>
> If the directory is changing while we're iterating through the 
> directory,
> POSIX does not require us to invalidate the page cache unless the user
> calls rewinddir(). However, we still do want to ensure that we use
> readdirplus in order to avoid a load of stat() calls when the user
> is doing an 'ls -l' workload.
>
> The fix should be to invalidate the page cache immediately when we're
> setting the NFS_INO_ADVISE_RDPLUS bit.
>
> Reported-by: Benjamin Coddington <bcodding@redhat.com>
> Fixes: 311324ad1713 ("NFS: Be more aggressive in using 
> readdirplus...")
> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>


Hi Trond, I apologize for the delay, thanks for these!  This one works 
as
expected.

Tested-by: Benjamin Coddington <bcodding@redhat.com>

Ben


> ---
>  fs/nfs/dir.c | 15 ++-------------
>  1 file changed, 2 insertions(+), 13 deletions(-)
>
> diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c
> index 5f1af4cd1a33..53e02b8bd9bd 100644
> --- a/fs/nfs/dir.c
> +++ b/fs/nfs/dir.c
> @@ -477,7 +477,7 @@ void nfs_force_use_readdirplus(struct inode *dir)
>  {
>  	if (!list_empty(&NFS_I(dir)->open_files)) {
>  		nfs_advise_use_readdirplus(dir);
> -		nfs_zap_mapping(dir, dir->i_mapping);
> +		invalidate_mapping_pages(dir->i_mapping, 0, -1);
>  	}
>  }
>
> @@ -886,17 +886,6 @@ int uncached_readdir(nfs_readdir_descriptor_t 
> *desc)
>  	goto out;
>  }
>
> -static bool nfs_dir_mapping_need_revalidate(struct inode *dir)
> -{
> -	struct nfs_inode *nfsi = NFS_I(dir);
> -
> -	if (nfs_attribute_cache_expired(dir))
> -		return true;
> -	if (nfsi->cache_validity & NFS_INO_INVALID_DATA)
> -		return true;
> -	return false;
> -}
> -
>  /* The file offset position represents the dirent entry number.  A
>     last cookie cache takes care of the common case of reading the
>     whole directory.
> @@ -928,7 +917,7 @@ static int nfs_readdir(struct file *file, struct 
> dir_context *ctx)
>  	desc->decode = NFS_PROTO(inode)->decode_dirent;
>  	desc->plus = nfs_use_readdirplus(inode, ctx) ? 1 : 0;
>
> -	if (ctx->pos == 0 || nfs_dir_mapping_need_revalidate(inode))
> +	if (ctx->pos == 0 || nfs_attribute_cache_expired(inode))
>  		res = nfs_revalidate_mapping(inode, file->f_mapping);
>  	if (res < 0)
>  		goto out;
> -- 
> 2.7.4

      parent reply	other threads:[~2016-11-30 19:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-19 16:54 [PATCH 0/3] Address readdirplus performance Trond Myklebust
2016-11-19 16:54 ` [PATCH 1/3] NFS: Fix a performance regression in readdir Trond Myklebust
2016-11-19 16:54   ` [PATCH 2/3] NFS: Be more targeted about readdirplus use when doing lookup/revalidation Trond Myklebust
2016-11-19 16:54     ` [PATCH 3/3] NFS: Replace nfs_force_use_readdirplus() with nfs_advise_use_readdirplus() Trond Myklebust
2016-11-30 19:09     ` [PATCH 2/3] NFS: Be more targeted about readdirplus use when doing lookup/revalidation Benjamin Coddington
2016-12-01 20:47       ` Trond Myklebust
2016-12-02 13:56         ` Benjamin Coddington
2016-12-02 14:32           ` Trond Myklebust
2016-11-30 19:08   ` Benjamin Coddington [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=F7498BF3-4642-49F1-9283-7881FBE56E20@redhat.com \
    --to=bcodding@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    /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.