diff options
author | Timothy Redaelli <tredaelli@redhat.com> | 2021-06-24 00:09:50 +0200 |
---|---|---|
committer | Ilya Maximets <i.maximets@ovn.org> | 2021-07-01 16:31:55 +0200 |
commit | 772a842fb5489c810a321457e53e384a6d607bfd (patch) | |
tree | d88e2152526e320b494b8f08d715f850c167167b /vswitchd | |
parent | 07a5fa610ee8284d8f147607eb5deec5f25e8ee7 (diff) | |
download | openvswitch-772a842fb5489c810a321457e53e384a6d607bfd.tar.gz |
dpif-netdev: Apply subtable-lookup-prio-set on any datapath.
Currently, if you try to set subtable-lookup-prio-set when you don't have
any datapath (for example if an user wants to set AVX512 before creating
any bridge) it sets it globally (dpcls_subtable_set_prio),
but it returns an error:
please specify an existing datapath
ovs-appctl: ovs-vswitchd: server returned an error
and, in this case, the exit code of ovs-appctl is 2.
This commit changes the behaviour by removing the [datapath] optional
parameter of subtable-lookup-prio-set and by changing the priority
level on any datapath and globally. This means if you don't have any
datapath or if you have only one datapath, the behaviour is the same as
now, but without the confusing error when you don't have any datapath.
Fixes: 3d018c3ea79d ("dpif-netdev: add subtable lookup prio set command.")
Signed-off-by: Timothy Redaelli <tredaelli@redhat.com>
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
Diffstat (limited to 'vswitchd')
0 files changed, 0 insertions, 0 deletions