Re: [vpp-dev] VPP dpdk interface placement from startup.conf

2018-04-17 Thread Damjan Marion
Are you aware of "show interface rx-placement" and "set interface rx-placement" CLIs? Can you capture output? -- Damjan > On 16 Apr 2018, at 17:26, Rogan Lynch wrote: > > Thank you Damjan, > > This syntax appears to parse without error, but somehow breaks allocation

Re: [vpp-dev] VPP dpdk interface placement from startup.conf

2018-04-16 Thread Rogan Lynch
Thank you Damjan, This syntax appears to parse without error, but somehow breaks allocation of the DPDK interfaces in our build. Thank you for letting me know about this option, obviously if you want to control which NUMA you land on VPP will need to provide some way to PIN these mappings in

Re: [vpp-dev] VPP dpdk interface placement from startup.conf

2018-04-15 Thread Damjan Marion
Dear Rogan, Long time ago I wrote a code to do exactly that, an code is still there, but i will not put my left hand into fire that it still works. syntax is: dpdk { dev :02:00.1 { num-rx-queues 2 workers 4,5 } } Let us know if it works...

[vpp-dev] VPP dpdk interface placement from startup.conf

2018-04-09 Thread Rogan Lynch
Hello folks, Just a newbie question that I hope can be put to rest quickly: Given that VPP distributes worker threads in round-robin fashion by default, but can have them reassigned post-facto via the terminal CLI, Is is possible to pin these threads a priori from a startup.conf param? Or do I