On Thu, 12 Oct 2000, James Simmons wrote:
>
> > > every CPU to avoid slowdowns. So that if you set that eth0's
> > > IRQ will be handled by CPU1, the MTRRs of CPU1 will be set
> > > accordingly, and the other CPUs will not care about eth0,
> > > so they do not need eth0's MTRR settings.
> >
> > A little question. Why do we want to bind irq of eth0 to a single CPU ?
> > imho it will casue slowdown of some situation. Why don't we leave scheduler
> > to select CPU for processing IRQ ?
>
> This would be really horrible for video cards. X would come to a crawl :-(
Why? You are not forced to exclude the videocard memory from MTRRs.
I meant things that make sense, e.g. 4 eth card, 4 CPUs, every CPU is
bound to one and only one eth, so only the relevant CPU needs to contain
an entry for the eth it is bound to. It may make sense.
Regards,
Zoltan Boszormenyi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Oct 15 2000 - 21:00:24 EST