From 4fb54652e010c4fc3d4e2d310c64465ffcad2c23 Mon Sep 17 00:00:00 2001 From: Kevin Traynor Date: Fri, 16 Jul 2021 17:02:08 +0100 Subject: 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 Acked-by: Sunil Pai G Acked-by: David Marchand Signed-off-by: Ian Stokes --- Documentation/topics/dpdk/pmd.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'Documentation') 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 ```` is not available (e.g. the - ```` is not in ``pmd-cpu-mask``), the RX queue will not be polled - by any PMD thread. + be polled. If the provided ```` is not available (e.g. the + ```` 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. -- cgit v1.2.1