From: Alexander Viro <viro@math.psu.edu>
To: Andrew Morton <akpm@zip.com.au>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
Mike Fedyk <mfedyk@matchmail.com>,
lkml <linux-kernel@vger.kernel.org>,
ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] disk throughput
Date: Mon, 5 Nov 2001 09:23:41 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.21.0111050904000.23204-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <3BE647F4.AD576FF2@zip.com.au>
On Mon, 5 Nov 2001, Andrew Morton wrote:
> OK, that's one possible reason. Not sure I buy it though. If
> the files are created a few days after their parent directory
> then the chance of their data or metadata being within device
> readhead scope of any of the parent dir's blocks seems small?
Algorithm for inode allocation had been written by Kirk back in
'84. You can find some analisys in the original paper (A Fast
Filesystem for UNIX).
BTW, what you want is not "readahead scope of parent dir block".
You want inodes of files in given directory close to each other.
That matters a lot when you do stat() on directory contents,
etc. Moreover, since we attempt to keep data blocks close to
inodes, we want to keep use of cylinder groups more or less
even.
next prev parent reply other threads:[~2001-11-05 14:24 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 2:13 disk throughput Andrew Morton
2001-11-05 3:20 ` Mohammad A. Haque
2001-11-05 3:31 ` Andrew Morton
2001-11-05 3:32 ` [Ext2-devel] " Mike Fedyk
2001-11-05 3:45 ` Andrew Morton
2001-11-05 4:39 ` Mike Fedyk
2001-11-05 7:06 ` Jens Axboe
2001-11-05 7:14 ` Andrew Morton
2001-11-05 7:26 ` Jens Axboe
2001-11-05 7:14 ` Mike Fedyk
2001-11-05 7:18 ` Jens Axboe
2001-11-05 7:18 ` Jens Axboe
2001-11-05 9:14 ` Mike Fedyk
2001-11-05 9:20 ` Jens Axboe
2001-11-05 5:54 ` Albert D. Cahalan
2001-11-05 8:04 ` Andrew Morton
2001-11-05 12:28 ` Matthias Andree
2001-11-05 14:23 ` Alexander Viro [this message]
2001-11-05 22:22 ` Andrew Morton
2001-11-05 22:41 ` Andreas Dilger
2001-11-05 22:53 ` Andrew Morton
2001-11-08 15:28 ` Constantin Loizides
2001-11-05 23:14 ` Dan Hollis
2001-11-06 10:52 ` Daniel Phillips
2001-11-06 16:17 ` Jeremy Fitzhardinge
2001-11-08 15:24 ` Constantin Loizides
2001-11-08 16:46 ` Jeremy Fitzhardinge
2001-11-09 6:08 ` Andrew Morton
2001-11-09 8:49 ` Jeremy Fitzhardinge
2001-11-06 21:45 ` Stephen Tweedie
2001-11-05 20:16 ` Andreas Dilger
2001-11-05 20:28 ` m
2001-11-05 21:39 ` Andrew Morton
2001-11-05 22:59 ` Linus Torvalds
2001-11-05 23:36 ` Alexander Viro
2001-11-05 23:50 ` Linus Torvalds
2001-11-06 0:03 ` Linus Torvalds
2001-11-06 1:33 ` Alexander Viro
2001-11-06 2:10 ` Linus Torvalds
2001-11-06 3:02 ` Alexander Viro
2001-11-06 8:39 ` Alan Cox
2001-11-06 8:37 ` Alexander Viro
2001-11-06 8:48 ` Andrew Morton
2001-11-06 3:49 ` Alexander Viro
2001-11-06 4:01 ` Linus Torvalds
2001-11-06 4:21 ` Alexander Viro
2001-11-06 5:01 ` Linus Torvalds
2001-11-06 5:31 ` Andrew Morton
2001-11-06 5:48 ` Linus Torvalds
2001-11-06 7:34 ` Mike Castle
2001-11-06 7:10 ` Kai Henningsen
2001-11-09 22:35 ` Riley Williams
2001-11-06 1:28 ` Alexander Viro
2001-11-06 9:16 ` Wojtek Pilorz
2001-11-06 9:58 ` Alexander Viro
2001-11-08 12:51 ` Pavel Machek
2001-11-06 21:48 ` Stephen Tweedie
2001-11-06 23:17 ` ext2/ialloc.c cleanup Alexander Viro
2001-11-07 19:34 ` [Ext2-devel] " Andreas Dilger
2001-11-07 20:02 ` Alexander Viro
2001-11-08 2:06 ` Andrew Morton
2001-11-08 20:45 ` Andrew Morton
2001-11-08 22:16 ` Alexander Viro
2001-11-08 22:43 ` Andreas Dilger
2001-11-08 23:08 ` Alexander Viro
2001-11-09 6:15 ` Andrew Morton
2001-11-09 6:56 ` Andreas Dilger
2001-11-09 7:09 ` Andrew Morton
2001-11-09 7:12 ` Alexander Viro
2001-11-09 7:18 ` Andrew Morton
2001-11-05 9:45 ` [Ext2-devel] disk throughput Alex Bligh - linux-kernel
2001-11-05 9:58 ` Alex Bligh - linux-kernel
2001-11-05 8:47 ` Jan Kara
2001-11-05 8:50 ` [Ext2-devel] " Mike Fedyk
2001-11-05 9:01 ` Jan Kara
2001-11-05 12:23 ` Matthias Andree
2001-11-05 22:39 ` Andrew Morton
2001-11-05 23:41 ` Matthias Andree
2001-11-12 6:04 [Ext2-devel] " Yan, Noah
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=Pine.GSO.4.21.0111050904000.23204-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=acahalan@cs.uml.edu \
--cc=akpm@zip.com.au \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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).