getaffinity/setaffinity and cpu sets.
ceri at submonkey.net
Thu Feb 21 22:54:01 UTC 2008
On Thu, Feb 21, 2008 at 09:27:41AM +0000, Robert Watson wrote:
> - You don't mention what happens if a process's cpu set changes to preclude a
> CPU the process has a thread with affinity for. Online, you suggested
> SIGKILL, and I thought maybe a new SIGCPUGONE with a default SIGKILL action
> might be a friendlier model. We should see what Solaris and others do here
> though. I like the idea that the affinity is a guarantee in userspace
> because it means that you can rely on it; I'm OK with the idea that your
> thread always runs on the CPUs you have affinity for unless in the
> SIGCPUGONE handler :-).
If a processor set disappears from under a process on Solaris, the
process gets moved to the "default" set (or, in other words, they aren't
in a set any more).
That must be wonderful! I don't understand it at all.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20080221/bbd3d6c5/attachment.pgp
More information about the freebsd-arch