Pinning an rxq to a PMD with pmd-rxq-affinity may be done for
various reasons such as reserving a full PMD for an rxq, or to
ensure that multiple rxqs from a port are handled on different PMDs.
Previously pmd-rxq-affinity always isolated the PMD so no other rxqs
could be assigned to it by OVS. The
Hi Kevin,
> Subject: [PATCH v4 6/7] dpif-netdev: Allow pin rxq and non-isolate PMD.
>
> Pinning an rxq to a PMD with pmd-rxq-affinity may be done for various
> reasons such as reserving a full PMD for an rxq, or to ensure that multiple
> rxqs from a port are handled on different PMDs.
>
> Pre
On Thu, Jul 8, 2021 at 3:54 PM Kevin Traynor wrote:
>
> Pinning an rxq to a PMD with pmd-rxq-affinity may be done for
> various reasons such as reserving a full PMD for an rxq, or to
> ensure that multiple rxqs from a port are handled on different PMDs.
>
> Previously pmd-rxq-affinity always isola
> -Original Message-
> From: dev On Behalf Of Kevin Traynor
> Sent: Thursday, 8 July, 2021 15:54
> To: d...@openvswitch.org
> Cc: david.march...@redhat.com
> Subject: [ovs-dev] [PATCH v4 6/7] dpif-netdev: Allow pin rxq and non-isolate
> PMD.
>
> Pinning a
Hi Jan,
On 13/07/2021 08:41, Jan Scheurich wrote:
>
>> -Original Message-
>> From: dev On Behalf Of Kevin Traynor
>> Sent: Thursday, 8 July, 2021 15:54
>> To: d...@openvswitch.org
>> Cc: david.march...@redhat.com
>> Subject: [ovs-dev] [PATCH v4
> >> +If using ``pmd-rxq-assign=group`` PMD threads with *pinned* Rxqs can
> >> +be
> >> +*non-isolated* by setting::
> >> +
> >> + $ ovs-vsctl set Open_vSwitch . other_config:pmd-rxq-isolate=false
> >
> > Is there any specific reason why the new pmd-rxq-isolate option should be
> limited to the "
