[rfc] bind per-cpu timeout threads to each CPU

Adrian Chadd adrian at freebsd.org
Thu Feb 20 21:48:07 UTC 2014


On 20 February 2014 11:17, John Baldwin <jhb at freebsd.org> wrote:

> (A further variant of this would be to divorce cpu0's swi from the
> catch-all softclock and let the catch-all softclock float, but bind
> all the per-cpu swis)

I like this idea. If something (eg per-CPU TCP timers, if it's turned
on) makes a very specific decision about the CPU then it should be
fixed. Otherwise a lot of the underlying assumptions for things like
RSS just aren't guaranteed to hold.

It could also perhaps extend to some abstract pool of CPUs later, if
we wanted to do things like one flowing swi per socket or whatnot when
we start booting on 1024 core boxes...

-a


More information about the freebsd-arch mailing list