General rule is that increasing those values are reducing number of rx drops due to VPP being de-scheduled or busy or due to traffic bursts, but also that degrades performance.
I think what we have set as default is reasonable and you should leave it unless you are experiencing some issues… — Damjan > On 14.04.2021., at 13:45, Marcos - Mgiga <mar...@mgiga.com.br> wrote: > > Hello Damjan, > > Thank you for clarifying... > > I also have a question about num-rx-desc and num-rt-desc parameters, hope you > dont mind to dicuss it in this e-mail > > I would like to understand what value fits better to my environment, do have > any thoughts about it? > > Best Regards > De: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> <vpp-dev@lists.fd.io > <mailto:vpp-dev@lists.fd.io>> Em nome de Damjan Marion via lists.fd.io > <http://lists.fd.io/> > Enviada em: quarta-feira, 14 de abril de 2021 08:24 > Para: Marcos - Mgiga <mar...@mgiga.com.br <mailto:mar...@mgiga.com.br>> > Cc: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> > Assunto: Re: [vpp-dev] TX Queue Placement > > > > > On 14.04.2021., at 13:21, Marcos - Mgiga <mar...@mgiga.com.br > <mailto:mar...@mgiga.com.br>> wrote: > > Hello, > > I increased VPP rx/tx queues in order to enable RSS on VPP instance. Since > VPP is running on a NUMA system with two threads with 8 cores each, I would > like to pin TX / RX queue to proper NUMA nodes. > > Using set interface rx-placement I was able to associate rx queue to desired > cores, so I would like to know if is there any possibility to pin tx queue to > a certain workers as well. > > > Not at the moment. tx queues are statically mapped (0 to main thread, 1 to > worker 0, 2 to worker 1, etc.). > There are some plans to implement such capability….. > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19194): https://lists.fd.io/g/vpp-dev/message/19194 Mute This Topic: https://lists.fd.io/mt/82088483/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
