Date: Fri, 09 May 2014 12:50:28 -0700 From: Peter Grehan <grehan@freebsd.org> To: Adrian Chadd <adrian@freebsd.org>, John Baldwin <jhb@freebsd.org> Cc: Alexander Motin <mav@freebsd.org>, freebsd-current <freebsd-current@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: [rfc] bind per-cpu timeout threads to each CPU Message-ID: <536D3184.9070302@freebsd.org> In-Reply-To: <CAJ-VmokL40MGY2=sKAtvgMBKHt6ZRY9ZfnZ1Mj5y1qAa4ANC=A@mail.gmail.com> References: <530508B7.7060102@FreeBSD.org> <CAJ-VmonUiSeCxnbYcjtWZ8uxa0c2ys5Za_GMLQenwu8zmEuFpQ@mail.gmail.com> <CAJ-VmonmrB7Z-PKH7P1DOJjSvFD_nRHqaiFJUuwvHoTUtiEVoQ@mail.gmail.com> <201405091349.14381.jhb@freebsd.org> <CAJ-VmokL40MGY2=sKAtvgMBKHt6ZRY9ZfnZ1Mj5y1qAa4ANC=A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> How about i instead do the comprimise: > > * i'll pin all other swi's > * default swi isn't pinned by default, but one can flip on a sysctl at > boot time to pin it > > How's that sound? And also please a sysctl that disables any swi pinning. It is sometimes useful to change the default cpuset, for instance to allocate a subset of CPUs to some particular applications and not FreeBSD. Having kernel threads pinned prevents this from happening since they are in the default set. (Note that some network drivers are also culprits here, though disabling MSI-x in them is a workaround). later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?536D3184.9070302>