[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0704280740010.16264@artax.karlin.mff.cuni.cz>
Date: Sat, 28 Apr 2007 07:45:52 +0200 (CEST)
From: Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>
To: Bill Huey <billh@...ppy.monkey.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Andreas Dilger <adilger@...sterfs.com>,
Marat Buharov <marat.buharov@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Mike Galbraith <efault@....de>,
LKML <linux-kernel@...r.kernel.org>,
Jens Axboe <jens.axboe@...cle.com>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
Alex Tomas <alex@...sterfs.com>
Subject: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS
is under heavy write load (massive starvation)
On Sat, 28 Apr 2007, Mikulas Patocka wrote:
> On Fri, 27 Apr 2007, Bill Huey wrote:
> Hi
>
> SpadFS doesn't write to unallocated parts like log filesystems (LFS) or
> phase tree filesystems (TUX2);
--- BTW, I don't think that writing to unallocated parts of disk is good
idea. These filesystems have cool write benchmarks, but one subtle (and
unbenchmarkable) problem:
They group files according to time when they were created and not
according to directory hierarchy.
When the user has directory with project files and he edited different
files at different times, normal filesystems will place the files near
each other (so that "grep blabla *" is fast) and log-structured
filesystems will scatter the files over the whole disk.
Mikulas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists