No subject

available in Linux. The effects you have (which ones exactly?) are probably 
cache effects in cases that a process is running on CPU X for one timeslot, 
and running on CPU Y for the next timeslot (loosing the cache contents of CPU 
X).

The Win32 API (sic!), and i.e. Solaris, have nice functions (see 
http://www.sybase.com/detail/1,6904,1010600,00.html) to do this, and this 
improves performances for certain scenarios (esp. 1:1 mapping of CPU-hungry 
processes). There's still much left to improve in the Linux kernel... 

 Joachim

-- 
Joachim Worringen - NEC C&C research lab St.Augustin
fon +49-2241-9252.20 - fax .99 - http://www.ccrl-nece.de