Re: XFS for 2.4

From: Clemens Schwaighofer
Date: Thu Dec 04 2003 - 05:14:56 EST

Hash: SHA1

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

| 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"

well I don't know, I don't use this box full time, but quite a lot, I do
a lot of compiling on it. Run Mozilla, etc on it, copy big files, etc,
but I never had any serious "lock" problems, where everthing freezes for
a second like I have from time to time in 2.4

|>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
| 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.

well on my working bux I run 2.4.22-ck3 and this has a lot of preempt
workstation speedup stuff inside, but it still freezes from time to time
if there is a peak in workload.

|>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.

well test11 is very smooth. I haven't tried Nick scheduler but I might
give it a shot, just to see how the "xterm craziness" goes ... :)

- --
Clemens Schwaighofer - IT Engineer & System Administration
Tequila Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


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