[lkml]   [2000]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectIRQ affinity vs. MTRRs, was Re: 36 bit MTRRs, Re: test10-pre1 problems on 4-way SuperServer8050
I came up with an idea. The MTRRs are per-cpu things.
Ingo Molnar's IRQ affinity code helps binding certain
IRQ sources to certain CPUs.

What if the MTRR driver allows per-CPU settings, maybe only on
uncached areas? Of course the real memory should be cached in
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.

Tell me if this is a highly stupid idea. :-)

Zoltan Boszormenyi

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

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