[lkml]   [2001]   [Dec]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Linux 2.4.17-pre5

> > Using the scheduler i'm working on and setting a trigger load level of 2,
> > as soon as the idle is scheduled it'll go to grab the task waiting on the
> > other cpu and it'll make it running.
> That rapidly gets you thrashing around as I suspect you've found.
> I'm currently using the following rule in wake up
> if(current->mm->runnable > 0) /* One already running ? */
> cpu = current->mm->last_cpu;

Is this really a win?

I mean, if I have two tasks that can run from L2 cache, I want them on
different physical CPUs even if they share current->mm, no?

"I do not steal MS software. It is not worth it."
-- Pavel Kankovsky
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:14    [W:0.087 / U:0.584 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site