numa and taskqueues
Adrian Chadd
adrian at freebsd.org
Tue May 30 14:46:32 UTC 2017
On 30 May 2017 at 03:56, Emeric POUPON <emeric.poupon at stormshield.eu> wrote:
> Hi,
>
>> Anyway - I think it'd be nice to have domain aware and pcpu aware
>> taskqueues so we can eventually migrate to a taskqueue group model of
>> "one top level things for net processing" for devices to share, etc,
>> etc. But for the short term just prototype it with some thin API in
>> crypto that wraps the taskqueue / kproc work so it gets done, then
>> push that work out for review/evaluation. if it does indeed work the
>> way you intend, we can try to use it as a template for a higher level,
>> shared taskqueue thing.
>
> It looks like it is somewhat mandatory to modify the taskqueue API to pin threads to the
> correct CPUs. The logic to define which CPU need to be set is another story that indeed can first
> be implemented in crypto(9).
>
> By the way:
> 1/ do you have some pointers on domain enumeration and other numa related code?
Sorry, I'm a bit too busy with other things to dive in right now :(
> 2/ about https://reviews.freebsd.org/D10680, I think it would be great to have this commited as a first step.
> Since it seems to be stuck, maybe I can add more people on this. Any suggestion?
Well, what's with the ~ 8% performance decrease? Do you know what's
going on? For a "we're parallelising IPSEC operations", seeing it get
slower with more flows is a bit concerning.
Thanks,
-adrian
More information about the freebsd-arch
mailing list