Re: XFS for 2.4

From: Willy Tarreau
Date: Thu Dec 04 2003 - 00:37:56 EST

On Thu, Dec 04, 2003 at 09:34:23AM +0900, Clemens Schwaighofer wrote:

> Well, I had to try that here. I've got a Celeron 650Mhz with 320MB ram
> and a crappy 14GB HD and yes the finds in the xterms are stopping for
> some time ... BUT X is 100% responsive. there is no sluggishness, I can
> use mozilla, etc without a problem. so seriously, who makes 10 finds at
> the same time and finds are read from FS (I have XFS) so it might be a
> problem with that.

This exact workload is probably not needed by anybody. But my concern is
that if it fails here, then possibily other realistic workloads will fail
too. But since it's hard to identify, that's why I'm waiting for distros
to ship first releases, and for a few people to tell us about particular
cases where they are annoyed. Ingo, Con, Nick and others obviously cannot
make the greatest scheduler in the world without valuable feedback. And
I have the feeling that all they got was "bad...bad...bad.. STOP!! don't
touch anything, XMMS is now great".

Production workloads are typically different. Perhaps my 10 xterms produce
the same type of load as 10 persons grepping gigs of logs from memory ?
And perhaps my "ls -ltr" produce the same workload as... someone searching
a recent file with "ls -ltr".

> So I don't think the scheduler is bad, I think it is
> great. When I switched to 2.5 the first time on that box it was like
> "WOW", so little swapping and KDE is so smooth ... thats so wow ...

I too think it's great and smoother than 2.4. It obviously makes a difference
if you use X (and I don't use these KDE, etc...). But the smoothness was
also brought to 2.4 by patches such as rmap, preempt, variable-hz. All of
them have been merged into 2.6, so we cannot deny that they helped too.

> But for your problem, it might get better for these kind of things in
> later versions :)

-test10 was NOK. I'll try test11, and when I've time I'll try Nick's
scheduler too.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at