> > [...]
> > Add a device capability bit for PMDs that can keep at least some
> > of the flow rules across restart. Without this capability behavior
> > is still unspecified, which is now explicitly stated.
> > Declare that the application can test for persitence of flow rules
> > of a particular
f Of Dmitry Kozlyuk
> > > Sent: Saturday, October 16, 2021 12:18 AM
> > > To: dev@dpdk.org
> > > Cc: Ori Kam ; Thomas Monjalon
> > > ; Yigit, Ferruh ;
> > > Andrew Rybchenko
> > > Subject: [dpdk-dev] [PATCH v2 1/5] ethdev: add capability to keep
>
> -Original Message-
> From: Zhang, Qi Z
> Sent: 18 октября 2021 г. 16:06
> To: Dmitry Kozlyuk ; dev@dpdk.org
> Cc: Ori Kam ; NBU-Contact-Thomas Monjalon
> ; Yigit, Ferruh ; Andrew
> Rybchenko
> Subject: RE: [dpdk-dev] [PATCH v2 1/5] ethdev: add capability to keep
> -Original Message-
> From: dev On Behalf Of Dmitry Kozlyuk
> Sent: Saturday, October 16, 2021 12:18 AM
> To: dev@dpdk.org
> Cc: Ori Kam ; Thomas Monjalon
> ; Yigit, Ferruh ; Andrew
> Rybchenko
> Subject: [dpdk-dev] [PATCH v2 1/5] ethdev: add capability
On 10/15/21 7:18 PM, Dmitry Kozlyuk wrote:
> Currently, it is not specified what happens to the flow rules when
> the device is stopped, possibly reconfigured, then started.
> If flow rules were kept, it could be convenient for application
> developers, because they wouldn't need to save and restor
Currently, it is not specified what happens to the flow rules when
the device is stopped, possibly reconfigured, then started.
If flow rules were kept, it could be convenient for application
developers, because they wouldn't need to save and restore them.
However, due to the number of flows and pos
6 matches
Mail list logo
