From: Theodore Tso <tytso@mit.edu>
To: Avi Kivity <avi@qumranet.com>
Cc: Ulrich Drepper <drepper@gmail.com>,
Soeren Sandmann <sandmann@daimi.au.dk>,
linux-kernel@vger.kernel.org
Subject: Re: stat benchmark
Date: Mon, 28 Apr 2008 09:31:30 -0400 [thread overview]
Message-ID: <20080428133130.GG30840@mit.edu> (raw)
In-Reply-To: <4815BC1E.6020805@qumranet.com>
On Mon, Apr 28, 2008 at 02:59:26PM +0300, Avi Kivity wrote:
>
> A readdirplus() could sort the inodes according to the filesystem's layout,
> and additionally issue the stats in parallel, so if you have multiple
> spindles you get significant additional speedup.
>
Well, sorting inodes is something readdir() could do, but it takes
potentially an unbounded amount of (non-swappable) kernel memory.
That's why it's messy.
And it wouldn't be hard to have flags (set by fcntl()) on the fd
returned by readdir() which which requests inode cache prefetching,
which would have the same net result, without needing to design a new
system call. So before designing a new system call, it might be worth
it to do some benchmarks to see how much of the cost is really in the
number of stat() system calls, in the warm cache case.
- Ted
next prev parent reply other threads:[~2008-04-28 13:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 20:59 stat benchmark Soeren Sandmann
2008-04-24 21:42 ` Carl Henrik Lunde
2008-04-24 21:44 ` Jan Engelhardt
2008-04-25 2:27 ` Justin Banks
2008-04-25 7:01 ` Christoph Hellwig
2008-04-25 19:48 ` Theodore Tso
2008-04-27 23:29 ` Soeren Sandmann
2008-04-28 0:13 ` Carl Henrik Lunde
2008-04-28 19:41 ` Alexander Larsson
2008-04-28 2:10 ` Theodore Tso
2008-04-27 22:40 ` Carl Henrik Lunde
2008-04-28 17:46 ` Zach Brown
2008-04-28 4:43 ` Ulrich Drepper
2008-04-28 11:53 ` Theodore Tso
2008-04-28 11:59 ` Avi Kivity
2008-04-28 13:31 ` Theodore Tso [this message]
2008-04-28 16:18 ` J. Bruce Fields
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=20080428133130.GG30840@mit.edu \
--to=tytso@mit.edu \
--cc=avi@qumranet.com \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sandmann@daimi.au.dk \
/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