diff options
| author | Kevin Traynor <ktraynor@redhat.com> | 2021-07-16 17:02:10 +0100 |
|---|---|---|
| committer | Ian Stokes <ian.stokes@intel.com> | 2021-07-16 16:51:57 +0100 |
| commit | 6193e03267c163096189ca935c6fd29a4ced7f11 (patch) | |
| tree | adfd8b3a77192641f8578354f32a0f5baa9e135b /Documentation/topics | |
| parent | 3dd050909a74229f024da30ae4800ede79883248 (diff) | |
| download | openvswitch-6193e03267c163096189ca935c6fd29a4ced7f11.tar.gz | |
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.
Previously pmd-rxq-affinity always isolated the PMD so no other rxqs
could be assigned to it by OVS. There may be cases where there is
unused cycles on those pmds and the user would like other rxqs to
also be able to be assigned to it by OVS.
Add an option to pin the rxq and non-isolate the PMD. The default
behaviour is unchanged, which is pin and isolate the PMD.
In order to pin and non-isolate:
ovs-vsctl set Open_vSwitch . other_config:pmd-rxq-isolate=false
Note this is available only with group assignment type, as pinning
conflicts with the operation of the other rxq assignment algorithms.
Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
Acked-by: Sunil Pai G <sunil.pai.g@intel.com>
Acked-by: David Marchand <david.marchand@redhat.com>
Signed-off-by: Ian Stokes <ian.stokes@intel.com>
Diffstat (limited to 'Documentation/topics')
| -rw-r--r-- | Documentation/topics/dpdk/pmd.rst | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/Documentation/topics/dpdk/pmd.rst b/Documentation/topics/dpdk/pmd.rst index 29ba53954..30040d703 100644 --- a/Documentation/topics/dpdk/pmd.rst +++ b/Documentation/topics/dpdk/pmd.rst @@ -101,8 +101,13 @@ like so: - Queue #2 not pinned - Queue #3 pinned to core 8 -PMD threads on cores where Rx queues are *pinned* will become *isolated*. This -means that this thread will only poll the *pinned* Rx queues. +PMD threads on cores where Rx queues are *pinned* will become *isolated* by +default. This means that this thread will only poll the *pinned* Rx queues. + +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 .. warning:: |