Paul Durrant wrote: > On 22/02/2008, Garrett D'Amore <[EMAIL PROTECTED]> wrote: >> This has been the subject of much debate/consternation. Part of the >> problem is that there doesn't seem to be just "one" answer. The reason >> is that there is a trade off between sharing per-socket resources >> between core, versus being able to make use of that sharing -- (keeping >> caches warm, etc.) >> >> Individual testing has found quite conflicting results across platforms >> and test loads for what is the "optimum" distribution of interrupts >> across CPU cores. >> >> I'd just say that this is an area that is "evolving", as we struggle to >> figure out what the best practice *should* be. >> > > One of the solutions we've come up with for Windows is to get an > interrupt on every CPU (up to the max. we can support) by using the > appropriate policy setting then we can screen the CPU information and > only use queues bound to the interrupt of distinct packages or caches. > So I think, providing the driver can get the appropriate information > about the CPUs then it can make an informed decision about which > interrupts to use. > > Paul >
So in the world of windows, does the OS provide driver the information on how many CPUs you have in the system, and the relationships among the cores and strands (sharing L1 or L2 cache, etc)? The "policy setting" you mentioned above, did you mean some policies the OS already support and driver picks one of them or do you mean the driver comes up with its own set of policies and select one based on the cpu information? If I am not mistaken, you are hoping the OS can provide cpu information. Can you be a little more specific on what type of info your driver would require, in order to make intelligent traffic routing decisions? Thanks, Wes _______________________________________________ driver-discuss mailing list driver-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/driver-discuss
