[ovs-dev] [PATCH v2 1/3] netdev: Dynamic per-port Flow API.
i.maximets at samsung.com
Mon Jul 1 10:46:28 UTC 2019
On 01.07.2019 13:24, Eli Britstein wrote:
> On 7/1/2019 1:13 PM, Ilya Maximets wrote:
>> On 30.06.2019 7:47, Eli Britstein wrote:
>>> This patch breaks ovs-dpctl dump-flows, when using TC offloads (kernel).
>>> I added a print in netdev_flow_dump_create, and flow_api is NULL when
>>> invoking ovs-dpctl dump-flows.
>>> I think new netdev objects are created to the ports (netdev_open), but
>>> not properly initialized.
>>> Could you please have a look?
>> Hi. This is a known thing that ovs-dpctl is no longer suitable for dumping
>> of HW offloaded flows. Please, use 'ovs-appctl dpctl/dump-flows' instead.
>> There was a patch for documentation in v4 of patch-set:
>> Here is the relevant thread:
>> However, I missed updating the NEWS about that change. Will send the patch
>> for this soon.
>> Best regards, Ilya Maximets.
> If that so, don't you think this should be either fixed or deprecated?
Fixing seems not possible, because ovs-dpctl is a standalone application
that works only with default configuration and HW offloading is disabled
Regarding deprecation, I'd like to remove all the functionality from ovs-dpctl
utility keeping only ability to remove system datapaths, since this, IMHO,
is the only useful function.
> Imagine some flows are in TC and some in OVS. I guess dpctl will only
> show the OVS ones.
Yes, and this is documented.
> I know about that appctl, but at least currently it misses some
> information in the dump like "dp" and "offloaded".
appctl and dpctl works through the same code in lib/dpctl.c. So, everything
is supported. If you don't see those fields, increase the verbosity with
Best regards, Ilya Maximets.
More information about the dev