netisr defered - active only one thread
Alexander V. Chernikov
melifaro at FreeBSD.org
Thu Feb 2 19:10:43 UTC 2012
On 02.02.2012 21:07, Ryan Stone wrote:
> 2012/2/2 Alexander V. Chernikov<melifaro at 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 ...
More information about the freebsd-net