On Mon, Oct 07, 2002 at 07:59:26PM -0700, Andrew Morton wrote:
> In the testing which I did, based on Keith Smith's traces, the
> current code really isn't very effective.
> What I did was to run his aging workload an increasing number of
> times. Then measured the fragmentation of the files which it
> left behind. I measured the fragmentation simply by timing
> how long it took to read all the files, and compared that to
> how long it took to read the same files when they had been laid
> down on a fresh fs.
What access pattern did you use when you read the files? Did you
sweep through filesystem directory by directory, or did you use some
other pattern (perhaps random)?
It would also be interesting to get a measure of fragmentation of the
filesystems as measured by e2fsck. This only measures file
fragmentation, and not file locality on a per-directory (or more
ideally per-directory tree, but establishing where the directory trees
are is difficult).
> > [ administrator hints ]
> Alas, nobody uses them :(
No one will use them if they are need to do so manually. But if we
can convert a few programs to use them, then it might work. And
people didn't much use madvise() when it was first introduced either,
but it doesn't mean that the existence of the interface was a bad
If the current algorithm is so bad, then maybe the trick is to use the
fast-growth optimized allocator as the default, *unless* given a hint
to do so via some magic mkdir flag. Then if certain programs, such as
adduser (when creating a home directory), "cp -r", "bk clone", tar,
etc. where modified to give hints that the a particular directory was
at the top of a directory tree, then slow-growth optimized allocator
could be used to spread apart directory trees. No, it's not perfect,
but it should be better not using any hints at all. (And yes, it will
take a while before the userpsace tools that provide said hints are
And if we don't have any user-space hints, then we default to the
fast-growth algorithm, which should make Linus happy. :-)
> Maybe a mount option? But I think the current algorithm should
> default to "off".
How about a mount option with the possible values: "fast", "slow",
"hinted", and "auto", with the default being "auto" or "hinted"?
(Where hinted utilizes user-space hints, and "auto" utilizes
user-space hints if present, plus some of the so-called ugly
hueristics which you had discussed?)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:25 EST