The standard way to identify is to have all physical CPU's listed first (0,1 in a dual CPU system) followed by the virtual CPU's (2,3)
Hmmm, looks like you are wrong... /proc/cpuinfo shows cpu 0,1 as being one physical id, and cpu 2,3 as being the other..
# cat /proc/cpuinfo
processor : 0
physical id : 0
processor : 1
physical id : 0
processor : 2
physical id : 3
processor : 3
physical id : 3(much kruft deleted)
> Prime95's INI file lets you set the affinity, so look in the settings > of the program to set that to the physical processors.
>
> I can only vouch for Win32 and how it numbers the processors, but I
> seem to recall that Linux numbered them the same way... All physical
> followed by all virtual. I could be wrong though. I sometimes am. :)
I don't know if the affinity stuff will work in linux, however... I found some kernel patches that ADD cpu affinity support to linux, but it was only folded into the master source as of 2.5.8 (and, presumably, 2.6.x) and I'm running 2.4.20 on these servers. I don't really want to mess with patching the kernel on these R&D servers, they are being used for database development.
meanwhile, watching the CPUs in TOP, the 2 instances are bouncing all over them every few seconds.
_________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
