lkml.org 
[lkml]   [1999]   [Apr]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: CPU affinity

> On Wed, 14 Apr 1999, Rik van Riel wrote:
>
> > I think it won't affect the code path or the scheduling
> > behaviour very much, except for the fact that it'll cause
> > processes to stick to their CPU much better.

> 'much better'?. Do you have any testcase that shows that we do not stick
> to CPUs well enough? I actually have recorded traces of full kernel builds
> and the like, and the number of 'bad' CPU switches was zero. I'm getting
> slightly tired of claims like the above, this isnt a Microsoft trade show
> after all ...

Yes I have a testcase. I usually use xosview to visualize the CPU
usage on my dual PII system. When I start a pure numbercrunching job,
I can see how the numbercruncher is sheduled out by xosview by any
screen update of xosview. The kernel sees then an idle CPU and
schedules the numbercruncher onto the other CPU. This looks like a
__perfect__ "numbercruncing ping pong".


Regards,

Mathias Froehlich

--
Mathias Fr"ohlich e-mail: frohlich@na.uni-tuebingen.de
Institut f"ur Mathematik, Universit"at T"ubingen, D-72076 T"ubingen

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

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