On Mon, Mar 16, 2009 at 6:02 AM, Christian Packmann <Christian.Packmann@xxxxxx> wrote: > Hard affinity can be very useful on SMT systems by scheduling one int-heavy > and one FP-heavy thread to the same core, to make maximum use of execution > resources. The problem with this kind of idea is that it makes the running assumption that you're in control of the entire widget, which is to say no other tasks are competing for the same resources. All it takes is a single busy higher priority thread getting scheduled on the same core and your careful tuning has gone out the window, since I guarantee that it will run faster if the scheduler is able to drop it onto an idle core on a different CPU than if it can't run at all, FSB latency or not. Regards, Rene