From 6193e03267c163096189ca935c6fd29a4ced7f11 Mon Sep 17 00:00:00 2001 From: Kevin Traynor Date: Fri, 16 Jul 2021 17:02:10 +0100 Subject: 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 Acked-by: Sunil Pai G Acked-by: David Marchand Signed-off-by: Ian Stokes --- vswitchd/vswitch.xml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) (limited to 'vswitchd') diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index cf6937501..c15053b25 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -548,6 +548,25 @@

+ +

+ Specifies if a CPU core will be isolated after being pinned with + an Rx queue. +

+ Set this value to false to non-isolate a CPU core after + it is pinned with an Rxq using pmd-rxq-affinity. This + will allow OVS to assign other Rxqs to that CPU core. +

+

+ The default value is true. +

+

+ This can only be false when pmd-rxq-assign + is set to group. +

+
+

-- cgit v1.2.1