Re: [dpdk-dev] [PATCH v2 2/2] ethdev: announce moving to general modify function

> > > Currently there is a dedicated modify function for each > > > field that the application wants to change. > > > For example: > > > rte_flow_action_type_set_tp_port to modify destination port of UDP/TCP. > > > rte_flow_action_type_set_ipv4_dst to modify destination of IPv4. > > > > > > A new f

Re: [dpdk-dev] [PATCH v2 2/2] ethdev: announce moving to general modify function

On Tue, Aug 3, 2021 at 11:35 PM Ajit Khaparde wrote: > > On Tue, Aug 3, 2021 at 1:58 AM Ori Kam wrote: > > > > Currently there is a dedicated modify function for each > > field that the application wants to change. > > For example: > > rte_flow_action_type_set_tp_port to modify destination port o

Re: [dpdk-dev] [PATCH v2 2/2] ethdev: announce moving to general modify function

On Tue, Aug 3, 2021 at 1:58 AM Ori Kam wrote: > > Currently there is a dedicated modify function for each > field that the application wants to change. > For example: > rte_flow_action_type_set_tp_port to modify destination port of UDP/TCP. > rte_flow_action_type_set_ipv4_dst to modify destination

[dpdk-dev] [PATCH v2 2/2] ethdev: announce moving to general modify function

Currently there is a dedicated modify function for each field that the application wants to change. For example: rte_flow_action_type_set_tp_port to modify destination port of UDP/TCP. rte_flow_action_type_set_ipv4_dst to modify destination of IPv4. A new function rte_flow_action_modify_field DPDK