Date: Thu, 21 Feb 2008 22:37:49 +0000 From: Ceri Davies <ceri@submonkey.net> To: Robert Watson <rwatson@FreeBSD.org> Cc: Daniel Eischen <deischen@freebsd.org>, David Xu <davidxu@freebsd.org>, Andrew Gallatin <gallatin@cs.duke.edu>, arch@freebsd.org Subject: Re: getaffinity/setaffinity and cpu sets. Message-ID: <20080221223749.GJ22033@submonkey.net> In-Reply-To: <20080221092011.J52922@fledge.watson.org> References: <Pine.GSO.4.64.0801122240510.15683@sea.ntplx.net> <20080112194521.I957@desktop> <20080219234101.D920@desktop> <20080220101348.D44565@fledge.watson.org> <20080220005030.Y920@desktop> <20080220105333.G44565@fledge.watson.org> <47BCEFDB.5040207@freebsd.org> <20080220175532.Q920@desktop> <20080220213253.A920@desktop> <20080221092011.J52922@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
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).
Ceri
--
That must be wonderful! I don't understand it at all.
-- Moliere
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)
iD8DBQFHvf09ocfcwTS3JF8RAkgyAKCjZPFk+FvbFmy45woBII+H/v4QuACfe7Rv
6b0H+pNwaAyfOnOm9HxUjMI=
=d5La
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080221223749.GJ22033>