Date: Thu, 02 Feb 2012 23:09:16 +0400 From: "Alexander V. Chernikov" <melifaro@FreeBSD.org> To: Ryan Stone <rysto32@gmail.com> Cc: freebsd-net@freebsd.org, =?UTF-8?B?0JrQvtC90YzQutC+0LIg0JXQstCz0LXQvdC40Lk=?= <kes-kes@yandex.ru>, Andrey Zonov <andrey@zonov.org> Subject: Re: netisr defered - active only one thread Message-ID: <4F2ADF5C.1030900@FreeBSD.org> In-Reply-To: <CAFMmRNznRgTU6sN%2BKmo4jg0AEMfWiQzzNt4LvMFpR9qTvGiqYQ@mail.gmail.com> References: <4F29A464.3080302@zonov.org> <4F29E2C8.5000909@FreeBSD.org> <4F2A2EAB.3010700@zonov.org> <1446971288.20120202105912@yandex.ru> <4F2AB0A9.70905@FreeBSD.org> <CAFMmRNznRgTU6sN%2BKmo4jg0AEMfWiQzzNt4LvMFpR9qTvGiqYQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02.02.2012 21:07, Ryan Stone wrote: > 2012/2/2 Alexander V. Chernikov<melifaro@freebsd.org>: >> P.S. it is also reasonable to set net.isr.bindthreads to 1 > > I really don't recommend setting this in any release. There is > currently a bug with binding kernel threads that causes unrelated > threads to be unnecessarily bound to CPUs. In the specific case of > net.isr.bindthreads this will cause(among others) the softclock > threads to all be bound to the same CPU, which may well obviate any > performance increase from binding the netisr threads. > As far as I understand, the only effect of setting bindthreads to 1 causes intr_event_bind() to bind soft netisr to appropriate CPU. Can you point me to ML discussion or some other info clarifying this bug? Okay, so one can manually bind those netisrs to CPUs using `procstat -t 0` and cpuset -l X -t ... -- WBR, Alexander
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F2ADF5C.1030900>