From: Benny Halevy <bhalevy@panasas.com>
To: Jim Rees <rees@umich.edu>
Cc: Andrew Klaassen <clawsoon@yahoo.com>, linux-nfs@vger.kernel.org
Subject: Re: Prioritizing readdirplus/getattr/lookup
Date: Mon, 04 Apr 2011 17:26:49 -0700 [thread overview]
Message-ID: <4D9A61C9.1030900@panasas.com> (raw)
In-Reply-To: <20110404230528.GA2624@merit.edu>
On 2011-04-04 16:05, Jim Rees wrote:
> Andrew Klaassen wrote:
>
> I've confirmed my earlier results using 2.6.37.5 on the server, though now
> the results are closer to 10 times worse than the Netapp on similar
> hardware rather than 100 times worse.
>
> A big improvement, but I'd still be interested to know if the server is
> capable of the getattr/readdirplus/lookup versus read/write tradeoffs that
> I'm looking for to bring "ls -l" speeds under load down to levels that
> won't make my users yell at me.
>
> What would be nice is if we could add a new system call that would do
> roughly what the nfs4 readdir rpc does. It would take a mask of requested
> file attributes, then return those attributes along with the directory
> entries. This would help "ls -l" but would also help all those chatty new
> gnome/kde user interface things that love to stat every file in every
> directory.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Like this? :)
http://www.opengroup.org/platform/hecewg/uploads/40/10903/posix_io_readdir+.pdf
See this for discussion:
http://www.spinics.net/lists/linux-fsdevel/msg03276.html
And this for other ideas ;-)
http://www.opengroup.org/platform/hecewg/
Benny
next prev parent reply other threads:[~2011-04-05 0:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 13:31 Prioritizing readdirplus/getattr/lookup Andrew Klaassen
[not found] ` <802792.85762.qm-GjowA9KT+PL5nGHA2nhOEg9VFclH1bkmQQ4Iyu8u01E@public.gmane.org>
2011-04-04 16:22 ` Steven Procter
2011-04-04 16:45 ` Andrew Klaassen
2011-04-04 22:10 ` Andrew Klaassen
2011-04-04 23:05 ` Jim Rees
2011-04-05 0:26 ` Benny Halevy [this message]
2011-04-05 0:39 ` Jim Rees
[not found] ` <20110405003944.GA31014-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
2011-04-05 13:30 ` Benny Halevy
2011-04-05 17:14 ` Garth Gibson
2011-04-05 19:11 ` Benny Halevy
2011-04-05 19:34 ` Jim Rees
2011-04-05 19:46 ` Benny Halevy
2011-04-06 0:06 ` Andrew Klaassen
2011-04-06 19:25 ` Andrew Klaassen
2011-04-07 14:00 ` Chuck Lever
2011-04-07 14:34 ` Andrew Klaassen
2011-04-07 14:36 ` Chuck Lever
2011-04-07 21:25 ` Andrew Klaassen
2011-04-07 21:49 ` Andrew Klaassen
2011-04-07 22:48 ` Murata, Dennis
2011-04-08 1:22 ` Andrew Klaassen
2011-04-08 15:17 ` Chuck Lever
2011-04-11 13:31 ` Andrew Klaassen
2011-04-05 19:48 ` Trond Myklebust
2011-04-05 19:52 ` Benny Halevy
2011-04-05 19:57 ` Trond Myklebust
2011-04-05 20:57 ` Benny Halevy
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=4D9A61C9.1030900@panasas.com \
--to=bhalevy@panasas.com \
--cc=clawsoon@yahoo.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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).