> > This forces updating of flow stat at the next re-validation, even for > > flows that are being created when the revalidation has already commenced. > > > > It enables reliable testing of fast path flow stats using ovs-appctl > > time/warp after flow creation. > > > > Signed-off-by: Jan Scheurich <[email protected]> > > What are the consequences of this change?
I have not seen any other consequence of this change other than that new datapath flow entries are immediately included in the first stats poll, which means the very first reading of flow stats after flow creation is more accurate than before. I cannot see any problem with that. All unit tests run fine. There should be no load increase. Without this change it was difficult to get deterministically correct flow stats in unit tests. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
