567
社区成员
发帖
与我相关
我的任务
分享请发表友善的回复…
发表回复
jdlsfl 2008-05-08
- 打赏
- 举报
谢谢
蒋晟 2008-04-30
- 打赏
- 举报
Depends on how the OS schedule threads to CPUs, and how applications set their threads' processor affinity
In windows, the operating system does the allocation for you based on cpu usage. You can set the affinity but, it will not determine which processor you run on. On the XBox 360, the affinity is needed otherwise the 360 will not allocate your thread to a seperate processor at all.
In Mac, threads with default affinity policy will be scheduled freely on any processor. These threads will be preferentially migrated to run on an idle processor. Threads with affinity tags will tend to remain in place.
In linux, you can froce the thread to migrate on the other cpu, by calling *_setaffinity() with different mask.
In windows, the operating system does the allocation for you based on cpu usage. You can set the affinity but, it will not determine which processor you run on. On the XBox 360, the affinity is needed otherwise the 360 will not allocate your thread to a seperate processor at all.
In Mac, threads with default affinity policy will be scheduled freely on any processor. These threads will be preferentially migrated to run on an idle processor. Threads with affinity tags will tend to remain in place.
In linux, you can froce the thread to migrate on the other cpu, by calling *_setaffinity() with different mask.
