RE: [PATCH v3] ethdev: add flow rule actions update API

2023-05-23 Thread Ori Kam
Hi Ferruh, > -Original Message- > From: Ferruh Yigit > Sent: Tuesday, May 23, 2023 1:34 PM > > On 5/23/2023 7:59 AM, Ori Kam wrote: > > Hi > > > >> -Original Message- > >> From: Ferruh Yigit > >> Sent: Monday, May 22, 2023 1:28 PM > >> > >> On 5/18/2023 10:48 PM, Alexander Kozyr

Re: [PATCH v3] ethdev: add flow rule actions update API

2023-05-23 Thread Ferruh Yigit
On 5/23/2023 7:59 AM, Ori Kam wrote: > Hi > >> -Original Message- >> From: Ferruh Yigit >> Sent: Monday, May 22, 2023 1:28 PM >> >> On 5/18/2023 10:48 PM, Alexander Kozyrev wrote: >>> Introduce the new rte_flow_update() API allowing users >>> to update the action list in the already exis

RE: [PATCH v3] ethdev: add flow rule actions update API

2023-05-23 Thread Ori Kam
Hi > -Original Message- > From: Ferruh Yigit > Sent: Monday, May 22, 2023 1:28 PM > > On 5/18/2023 10:48 PM, Alexander Kozyrev wrote: > > Introduce the new rte_flow_update() API allowing users > > to update the action list in the already existing rule. > > If the API is only to update

Re: [PATCH v3] ethdev: add flow rule actions update API

2023-05-22 Thread Ferruh Yigit
On 5/18/2023 10:48 PM, Alexander Kozyrev wrote: > Introduce the new rte_flow_update() API allowing users > to update the action list in the already existing rule. If the API is only to update actions, does make sense to rename it to explicitly state this, like: `rte_flow_action_update()` Same for

RE: [PATCH v3] ethdev: add flow rule actions update API

2023-05-21 Thread Ori Kam
Hi Alexander, > -Original Message- > From: Alexander Kozyrev > Sent: Friday, May 19, 2023 12:49 AM > > Introduce the new rte_flow_update() API allowing users > to update the action list in the already existing rule. > Flow rules can be updated now without the need to destroy > the rule f