diff options
| author | Kevin Traynor <ktraynor@redhat.com> | 2021-07-16 17:02:08 +0100 |
|---|---|---|
| committer | Ian Stokes <ian.stokes@intel.com> | 2021-07-16 16:51:35 +0100 |
| commit | 4fb54652e010c4fc3d4e2d310c64465ffcad2c23 (patch) | |
| tree | eb94b8d499be55bc7f887171bd6f4f78ecb52a72 /Documentation/topics | |
| parent | 0efefc4f985190ee317eb9e1eb03b46aae9bd429 (diff) | |
| download | openvswitch-4fb54652e010c4fc3d4e2d310c64465ffcad2c23.tar.gz | |
dpif-netdev: Assign PMD for failed pinned rxqs.
Previously, if pmd-rxq-affinity was used to pin an rxq to
a core that was not in pmd-cpu-mask the rxq was not polled
for and the user received a warning. This meant that no traffic
would be received from that rxq.
Now that pinned and non-pinned rxqs are assigned to PMDs in
a common call to rxq scheduling, if an invalid core is
selected in pmd-rxq-affinity the rxq can be assigned an
available PMD (if any).
A warning will still be logged as the requested core could
not be used.
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 | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/topics/dpdk/pmd.rst b/Documentation/topics/dpdk/pmd.rst index e481e7941..065bd16ef 100644 --- a/Documentation/topics/dpdk/pmd.rst +++ b/Documentation/topics/dpdk/pmd.rst @@ -107,9 +107,9 @@ means that this thread will only poll the *pinned* Rx queues. .. warning:: If there are no *non-isolated* PMD threads, *non-pinned* RX queues will not - be polled. Also, if the provided ``<core-id>`` is not available (e.g. the - ``<core-id>`` is not in ``pmd-cpu-mask``), the RX queue will not be polled - by any PMD thread. + be polled. If the provided ``<core-id>`` is not available (e.g. the + ``<core-id>`` is not in ``pmd-cpu-mask``), the RX queue will be assigned to + a *non-isolated* PMD, that will remain *non-isolated*. If ``pmd-rxq-affinity`` is not set for Rx queues, they will be assigned to PMDs (cores) automatically. |