On 2/2/2023 1:47 PM, Gregory Etelson wrote: > Current API allows either query or update indirect flow action. > If indirect action must be conditionally updated according to it's > present state application must first issue action query then > analyze returned data and if needed issue update request. > When the update will be processed, action state can change and > the update can invalidate the action. > > Add `rte_flow_action_handle_query_update` function call, > and it's async version `rte_flow_async_action_handle_query_update` > to atomically query and update flow action. > > Application can control query and update order, if that is supported > by port hardware, by setting `qu_mode` parameter to > RTE_FLOW_QU_QUERY_FIRST or RTE_FLOW_QU_UPDATE_FIRST. > > Signed-off-by: Gregory Etelson <getel...@nvidia.com> > Acked-by: Ori Kam <or...@nvidia.com>
Series applied to dpdk-next-net/main, thanks. <...> > --- a/doc/guides/rel_notes/release_23_03.rst > +++ b/doc/guides/rel_notes/release_23_03.rst > @@ -78,6 +78,14 @@ New Features > ``rte_event_dev_config::nb_single_link_event_port_queues`` parameter > required for eth_rx, eth_tx, crypto and timer eventdev adapters. > > +* **Added functions to atomically query and update indirect flow action.** > + > + Added synchronous and asynchronous functions to atomically query and update > + indirect flow action: > + > + - ``rte_flow_action_handle_query_update`` > + - ``rte_flow_async_action_handle_query_update`` > + > I updated the location of release notes update while merging, but can you please pay attention to the order documented in the section comment next time? Same for both patches.
