Isn't this a linux kernel issue ?
My understanding is that the scheduler doesn't know that 2 of the CPU's
are actually the same underlying hardware and sometimes two contexts end
up fighting for the same underlying chip?
--dc--
On Thu, 2004-04-15 at 16:37, Josh Berkus wrote:
> Folks,
>
> > I am currently chasing what seems to be the same issue: massive context
> > swapping on a dual Xeon system. I tried back-patching the above-mentioned
> > patch ... it helps a little but by no means solves the problem ...
>
> BTW, I'm currently pursuing the possibility that this has something to do with
> the ServerWorks chipset on those motherboards. If anyone knows a high-end
> hardware+linux kernel geek I can corner, I'd appreciate it.
>
> Maybe I should contact OSDL ...
--
Dave Cramer
519 939 0336
ICQ # 14675561
