From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] Address readdirplus performance
Date: Sat, 19 Nov 2016 11:54:54 -0500 [thread overview]
Message-ID: <1479574497-38268-1-git-send-email-trond.myklebust@primarydata.com> (raw)
Attempt to address two performance issues:
1) The regression pointed out by Ben when doing 'ls -l' on a directory
that is being modified.
2) When using readdir() to iterate through a directory, avoid lookups
using the same method we use to avoid attribute revalidation.
The last patch is a cleanup.
Trond Myklebust (3):
NFS: Fix a performance regression in readdir
NFS: Be more targeted about readdirplus use when doing
lookup/revalidation
NFS: Replace nfs_force_use_readdirplus() with
nfs_advise_use_readdirplus()
fs/nfs/dir.c | 47 ++++++++++++++---------------------------------
fs/nfs/inode.c | 2 +-
fs/nfs/internal.h | 2 +-
3 files changed, 16 insertions(+), 35 deletions(-)
--
2.7.4
next reply other threads:[~2016-11-19 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 16:54 Trond Myklebust [this message]
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 ` [PATCH 1/3] NFS: Fix a performance regression in readdir Benjamin Coddington
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=1479574497-38268-1-git-send-email-trond.myklebust@primarydata.com \
--to=trond.myklebust@primarydata.com \
--cc=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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.