[dpdk-dev] [RFC] ethdev: introduce action context APIs

Bing Zhao bingz at nvidia.com
Tue Apr 6 11:07:43 CEST 2021


Hi Thomas and Andrew,

> -----Original Message-----
> From: Andrew Rybchenko <andrew.rybchenko at oktetlabs.ru>
> Sent: Monday, March 22, 2021 10:55 PM
> To: NBU-Contact-Thomas Monjalon <thomas at monjalon.net>; Bing Zhao
> <bingz at nvidia.com>
> Cc: Ori Kam <orika at nvidia.com>; ferruh.yigit at intel.com; dev at dpdk.org
> Subject: Re: [RFC] ethdev: introduce action context APIs
> 
> External email: Use caution opening links or attachments
> 
> 
> On 3/17/21 11:28 AM, Thomas Monjalon wrote:
> > 17/03/2021 08:59, Bing Zhao:
> >> The new functions rte_flow_action_ctx* that were added will
> replace
> >> the curret shared functions rte_flow_shared_action_*.
> >>   - rte_flow_shared_action_create
> >>   - rte_flow_shared_action_destroy
> >>   - rte_flow_shared_action_update
> >>   - rte_flow_shared_action_query
> >>   + rte_flow_action_ctx_create
> >>   + rte_flow_action_ctx_destroy
> >>   + rte_flow_action_ctx_update
> >>   + rte_flow_action_ctx_query
> >>
> >> When creating a action context, it could be shared among
> different
> >> flows or different ports. Or it could also be used by a single
> flow.
> >> The name "shared" is improper in a sense.
> >
> > Is it the only reason for the change?
> > I better understand "shared" even if it is sometimes not shared.
> 
> +1

In another email, I explained the change a bit more. Please check and give comments, thank you all.

BR. Bing


More information about the dev mailing list