[lkml]   [2003]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] "HT scheduler", sched-2.5.63-B3
At 12:10 AM 3/7/2003 -0800, Andrew Morton wrote:
>Mike Galbraith <> wrote:
> >
> > ...
> > Best would be for other testers to run some tests. With the make -j30
> > weirdness, I _suspect_ that other oddities (hmm... multi-client db load...
> > query service time) will show.
> >
>Yes, this is the second surprise interaction between the CPU scheduler
>and the IO system.
>Perhaps. In your case it seems that you're simply unable to generate
>the amount of concurrency which you used to. Which would make it purely
>a CPU scheduler thing.

Yes, of this I'm sure.

>It is not necessarily a bad thing (unless your total runtime has increased?)
>but we need to understand what has happened.

Total system throughput is fine, and as expected, the only difference is
the modest overhead of paging heftily or lightly and/or not at all. The
realtime throughput difference between kernels is ~10 seconds... very
definitely concurrency issue imvho. And I agree 100% that this is not
_necessarily_ a bad thing. The time it takes for _any_ pressure to build
looks decidedly bad though. With the combo patch it does look better than
earlier patches... sudden bursts of paging do not occurr, it's.....
smoother once it starts acting something resembling normal.

>What filesystem are you using?

The build is running in a small EXt2 partition.


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

 \ /
  Last update: 2005-03-22 13:33    [W:0.060 / U:5.988 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site