Re: [PATCH] cpu-freq: add troubleshooting section for FSB changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



in addition, most FSB systems have the memory controller in the chipset,
next to the PCI logic... so that the FSB bus for DMA transactions only
carries the snoop traffic, not the whole data.
So when should people look at this?

at this point the atheros folks haven't even confirmed that this is the cause...

I'm not saying that the linux behavior is optimal with P states (I have a rather
sizeable algorithm rewrite in the queue) but to blame anything and everything on
a half-speed FSB during a very idle system?
I'm still somewhat skeptical. Again.. the CPU is basically idle here (otherwise
ondemand would ramp the freq up quickly); at which point the FSB traffic mostly is
just cache coherency traffic.... much less bandwidth intensive.
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Devel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Forum]     [Linux SCSI]

  Powered by Linux