Date: Thu, 2 Feb 2012 12:07:24 -0500 From: Ryan Stone <rysto32@gmail.com> To: "Alexander V. Chernikov" <melifaro@freebsd.org> Cc: freebsd-net@freebsd.org, =?KOI8-R?B?68/O2MvP1yDl18fFzsnK?= <kes-kes@yandex.ru>, Andrey Zonov <andrey@zonov.org> Subject: Re: netisr defered - active only one thread Message-ID: <CAFMmRNznRgTU6sN%2BKmo4jg0AEMfWiQzzNt4LvMFpR9qTvGiqYQ@mail.gmail.com> In-Reply-To: <4F2AB0A9.70905@FreeBSD.org> References: <4F29A464.3080302@zonov.org> <4F29E2C8.5000909@FreeBSD.org> <4F2A2EAB.3010700@zonov.org> <1446971288.20120202105912@yandex.ru> <4F2AB0A9.70905@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNznRgTU6sN%2BKmo4jg0AEMfWiQzzNt4LvMFpR9qTvGiqYQ>