From: Steve Dickson <SteveD@redhat.com>
To: Rishi Agrawal <Rishi_Agrawal@symantec.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Cc: Rajesh Ghanekar <Rajesh_Ghanekar@symantec.com>,
Ram Pandiri <ram_pandiri@symantec.com>,
Sreeharsha Sarabu <Sreeharsha_Sarabu@symantec.com>,
Abhijit Dey <Abhijit_Dey@symantec.com>,
Tushar Shinde <Tushar_Shinde@symantec.com>,
"bfields@redhat.com" <bfields@redhat.com>
Subject: Re: Patch For Making Readdir_plus configurable
Date: Mon, 04 Aug 2014 10:31:09 -0400 [thread overview]
Message-ID: <53DF992D.6090404@RedHat.com> (raw)
In-Reply-To: <20AEB6A025F81A4288597093171D1B5719CF5813D2@APJ1XCHEVSPIN35.SYMC.SYMANTEC.COM>
Hello,
On 25/07/14 12:19, Rishi Agrawal wrote:
> Hi,
> One of our customer's application only needs file names not
> file attributes. With directories having 10K+ inodes (assuming buffer
> cache has directory blocks cached having file names, but inode
> cache is limited and hence need eviction of older cached inodes),
> older inodes are evicted periodically. So if they keep on doing
> readdir(2) from NSF client on multiple directories, some directory's
> files are periodically removed from inode cache and hence new
> readdir(2) on same directory requires disk access to bring back
> inodes again to inode cache.
>
> As READDIRPLUS request fetches attributes also, doing getattr on
> each file on server, it causes unnecessary disk accesses. If
> READDIRPLUS on NFS client is returned with -ENOTSUPP, NFS
> client uses READDIR request which just gets the names of the files
> in a directory, not attributes, hence avoiding disk accesses on server.
>
> Can this be per-export tunable so that different application can
> use it in different ways, some supporting readdirplus and others
> not supporting readdirplus?
>
> I have worked on a patch against 3.15.6 for this. Also I am
> adding a patch against latest nfs-utils to have an export option
> for this. Can someone let me know if these patches are adequate
> or if any other changes are required. Patches attached, although
> with minimal testing. I would like to know if something like this
> can be added and if the patch can be reworked if I am missing
> something for NFSv4.
I just notice that the nfs-utils patch does not update
the exports(5) man page. In that update please note
this is a v3 only thing.... Not clear what we are going
to do in the v4 case.
Finally, please inline your patch posting in the your
email as its is explained there
https://www.kernel.org/doc/Documentation/SubmittingPatches
It just makes it easier for everyone to do the review...
tia,
steved.
next prev parent reply other threads:[~2014-08-04 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 16:19 Patch For Making Readdir_plus configurable Rishi Agrawal
2014-07-25 16:54 ` Christopher T Vogan
[not found] ` <OF57CEB932.B84FFC9B-ON87257D20.005C9233-86257D20.005CC28D@us.ibm.com>
2014-07-28 3:17 ` Rishi Agrawal
2014-07-29 20:34 ` J. Bruce Fields
2014-08-04 14:31 ` Steve Dickson [this message]
2014-08-04 15:24 ` [PATCH] nfsd: allow turning off nfsv3 readdir_plus J. Bruce Fields
2014-08-04 21:46 ` J. Bruce Fields
2014-08-05 18:21 ` J. Bruce Fields
2014-08-18 17:47 ` Rajesh Ghanekar
2014-08-18 18:06 ` Rajesh Ghanekar
2014-08-18 19:10 ` J. Bruce Fields
2014-08-18 21:19 ` J. Bruce Fields
2014-08-18 21:42 ` Abhijit Dey
2014-08-19 7:53 ` Rajesh Ghanekar
2014-08-05 6:58 ` Patch For Making Readdir_plus configurable Rishi Agrawal
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=53DF992D.6090404@RedHat.com \
--to=steved@redhat.com \
--cc=Abhijit_Dey@symantec.com \
--cc=Rajesh_Ghanekar@symantec.com \
--cc=Rishi_Agrawal@symantec.com \
--cc=Sreeharsha_Sarabu@symantec.com \
--cc=Tushar_Shinde@symantec.com \
--cc=bfields@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=ram_pandiri@symantec.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 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).