Date: Mon, 6 Feb 2012 09:30:31 -0500 From: John Baldwin <jhb@freebsd.org> To: Ivan Voras <ivoras@freebsd.org> Cc: svn-src-head@freebsd.org, Ryan Stone <rstone@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org Subject: Re: svn commit: r230984 - head/sys/kern Message-ID: <201202060930.31511.jhb@freebsd.org> In-Reply-To: <CAF-QHFXQXqFskmMU%2BYxqmFEVKOoiHGMdnHBkSjqaEVZmjs_ovQ@mail.gmail.com> References: <201202041649.q14GnUnI043572@svn.freebsd.org> <CAF-QHFXQXqFskmMU%2BYxqmFEVKOoiHGMdnHBkSjqaEVZmjs_ovQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, February 06, 2012 6:34:06 am Ivan Voras wrote: > On 4 February 2012 17:49, Ryan Stone <rstone@freebsd.org> wrote: > > Author: rstone > > Date: Sat Feb 4 16:49:29 2012 > > New Revision: 230984 > > URL: http://svn.freebsd.org/changeset/base/230984 > > > > Log: > > Whenever a new kernel thread is spawned, explicitly clear any CPU affinity > > set on the new thread. This prevents the thread from inadvertently > > inheriting affinity from a random sibling. > > Shouldn't new threads inherit affinity from the threads which spawned them? User threads still do, but kernel threads are a bit tricky since most of them get created during boot when everything is running on the BSP, so the affinity they would inherit is rather bogus. Even post-boot many of the cases I can think of when you would create kthreads (e.g. expanding a thread pool), you don't really want to inherit affinity. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202060930.31511.jhb>