Jeff,
The utilBindThreadToCPU(x) function is part of a private framework,
CHUD.framework, that is installed in
/System/Library/PrivateFrameworks. Apple provides but does not
support this framework. Any part of it could be changed or removed in
future releases of CHUD without any notice or deprec
Just curious -- in regards to utilBindThreadToCPU(x), why does the
text say:
"That function should never go in a shipping app, but it’s useful
for debugging."
On Apr 28, 2008, at 4:30 PM, Brian Taylor wrote:
Actually, there is an unofficial processor affinity API on Mac OS X,
but it
Actually, there is an unofficial processor affinity API on Mac OS X,
but it is supplied only with the CHUD framework. I suppose as a
further barrier to using this API in code outside of Apple, the header
files for this API are only available with the standalone CHUD
installer. See:
http://lists.a
Things have not changed with Leopard. :-(
On Apr 23, 2008, at 6:26 PM, Alberto Giannetti wrote:
Note: I'm running Tiger (Darwin 8.11.1). Things might have changed
with Leopard.
On Apr 23, 2008, at 5:30 PM, Jeff Squyres wrote:
On Apr 23, 2008, at 3:01 PM, Alberto Giannetti wrote:
I would li
Note: I'm running Tiger (Darwin 8.11.1). Things might have changed
with Leopard.
On Apr 23, 2008, at 5:30 PM, Jeff Squyres wrote:
On Apr 23, 2008, at 3:01 PM, Alberto Giannetti wrote:
I would like to run one of my MPI processors to a single core on my
iMac Intel Core Duo system. I'm using re
On Apr 23, 2008, at 3:01 PM, Alberto Giannetti wrote:
I would like to run one of my MPI processors to a single core on my
iMac Intel Core Duo system. I'm using release 1.2.4 on Darwin 8.11.1.
It looks like processor affinity is not supported for this kind of
configuration:
I'm afraid that OS X
I would like to run one of my MPI processors to a single core on my
iMac Intel Core Duo system. I'm using release 1.2.4 on Darwin 8.11.1.
It looks like processor affinity is not supported for this kind of
configuration:
$ ompi_info|grep affinity
MCA maffinity: first_use (MCA v1.
