[lkml]   [2001]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] scheduler cache affinity improvement for 2.4 kernels
[cc trimed]

On Thu, Nov 08, 2001 at 04:37:46PM -0800, Davide Libenzi wrote:
> On Thu, 8 Nov 2001, Mike Fedyk wrote:
> > Ingo's patch in effect lowers the number of jiffies taken per second in the
> > scheduler (by making each task use several jiffies).
> >
> > Davide's patch can take the default scheduler (even Ingo's enhanced
> > scheduler) and make it per processor, with his extra layer of scheduling
> > between individual processors.
> Don't mix things :)
> We're talking only about the CpuHistory token of the scheduler proposed here:
> This is a bigger ( and not yet complete ) change on the SMP scheduler
> behavior, while it keeps the scheduler that runs on each CPU the same.
> I'm currently working on different balancing methods to keep the proposed
> scheduler fair well balanced without spinning tasks "too much"(tm).
I've given your patch a try, and so far it looks promising.

Running one niced copy of cpuhog on a 2x366 mhz celeron box did pretty well.
Instead of switching several times in one second, it only switched a few
times per minute.

I was also able to merge it with just about everything else I was testing
(ext3, freeswan, elevator updates, -ac) except for the preempt patch. Well, I
was able to manually merge it, but the cpu afinity broke. (it wouldn't use
the second processor for anything except for interrupt processing...)

I haven't tried any of the other scheduler patches though. MQ, looks
interesting... :)

All in all, I think xsched will have much more impact on performance.
Simply because it tackles the problem of CPU affinity...

Even comparing Ingo's patch to your CPU History patch isn't fair, because
they attack different problems. Yours of CPU affinity, Ingo's of time spent
on individual tasks within a single processor.

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:13    [W:0.104 / U:0.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site