On Sunday, September 21, 2003, at 04:31  AM, Matthias Scheler wrote:

> In article <86634305-EBA9-11D7-82A5-000A957650EC@wasabisystems.com>,
> 	Jason Thorpe <thorpej@wasabisystems.com> writes:
>> The real issue is that the scheduler needs to be aware of HTT in order
>> to make effective use of it.  Just treating it as a normal second CPU
>> will actually make the situation worse.
>
> While this is true for a dual Xeon HT system (where the scheduler could
> end up leaving a physical CUP unused) I don't see how that could affect
> a P4 HT system because there is only one physical CPU anyway.

It's very true for any HTT system with multiple physical CPUs.  As for 
a system with only a single physical CPU, what you really want in that 
case is to execute another thread *of the same program* on the other 
virtual CPU.

         -- Jason R. Thorpe <thorpej@wasabisystems.com>