Re: [ovs-dev] [PATCH v5] ofproto-dpif-upcall: Wait for valid hw flow stats before applying min-revalidate-pps

2023-03-08 Thread Eelco Chaudron
On 3 Mar 2023, at 22:20, Ilya Maximets wrote: > On 2/27/23 15:58, Eelco Chaudron wrote: >> Depending on the driver implementation, it can take from 0.2 seconds >> up to 2 seconds before offloaded flow statistics are updated. This is >> true for both TC and rte_flow-based offloading. This is

Re: [ovs-dev] [PATCH v5] ofproto-dpif-upcall: Wait for valid hw flow stats before applying min-revalidate-pps

2023-03-03 Thread Ilya Maximets
On 2/27/23 15:58, Eelco Chaudron wrote: > Depending on the driver implementation, it can take from 0.2 seconds > up to 2 seconds before offloaded flow statistics are updated. This is > true for both TC and rte_flow-based offloading. This is causing a > problem with min-revalidate-pps, as old

Re: [ovs-dev] [PATCH v5] ofproto-dpif-upcall: Wait for valid hw flow stats before applying min-revalidate-pps

2023-02-27 Thread Simon Horman
On Mon, Feb 27, 2023 at 03:58:04PM +0100, Eelco Chaudron wrote: > Depending on the driver implementation, it can take from 0.2 seconds > up to 2 seconds before offloaded flow statistics are updated. This is > true for both TC and rte_flow-based offloading. This is causing a > problem with

[ovs-dev] [PATCH v5] ofproto-dpif-upcall: Wait for valid hw flow stats before applying min-revalidate-pps

2023-02-27 Thread Eelco Chaudron
Depending on the driver implementation, it can take from 0.2 seconds up to 2 seconds before offloaded flow statistics are updated. This is true for both TC and rte_flow-based offloading. This is causing a problem with min-revalidate-pps, as old statistic values are used during this period. This