Re: [dpdk-dev] [PATCH v4 2/6] ethdev: add capability to keep shared objects on restart

2021-11-01 Thread Andrew Rybchenko
On 10/21/21 9:34 AM, Dmitry Kozlyuk wrote: rte_flow_action_handle_create() did not mention what happens with an indirect action when a device is stopped and started again. It is natural for some indirect actions, like counter, to be persistent. Keeping others at least saves application time and c

Re: [dpdk-dev] [PATCH v4 2/6] ethdev: add capability to keep shared objects on restart

2021-10-21 Thread Ajit Khaparde
On Wed, Oct 20, 2021 at 11:35 PM Dmitry Kozlyuk wrote: > > rte_flow_action_handle_create() did not mention what happens > with an indirect action when a device is stopped and started again. > It is natural for some indirect actions, like counter, to be persistent. > Keeping others at least saves a

Re: [dpdk-dev] [PATCH v4 2/6] ethdev: add capability to keep shared objects on restart

2021-10-21 Thread Ori Kam
Hi Dmitry, > -Original Message- > From: Dmitry Kozlyuk > Sent: Thursday, October 21, 2021 9:35 AM > Subject: [PATCH v4 2/6] ethdev: add capability to keep shared objects on > restart > > rte_flow_action_handle_create() did not mention what happens > with an indirect action when a device

[dpdk-dev] [PATCH v4 2/6] ethdev: add capability to keep shared objects on restart

2021-10-20 Thread Dmitry Kozlyuk
rte_flow_action_handle_create() did not mention what happens with an indirect action when a device is stopped and started again. It is natural for some indirect actions, like counter, to be persistent. Keeping others at least saves application time and complexity. However, not all PMDs can support