> > @@ -1445,6 +1450,8 @@ struct rte_eth_conf {
> > #define RTE_ETH_DEV_CAPA_RUNTIME_RX_QUEUE_SETUP 0x0001
> > /** Device supports Tx queue setup after device started. */
> > #define RTE_ETH_DEV_CAPA_RUNTIME_TX_QUEUE_SETUP 0x0002
> > +/** Device supports keeping flow rules across rest
On 10/21/21 9:34 AM, Dmitry Kozlyuk wrote:
Previously, it was 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 th
On Wed, Oct 20, 2021 at 11:35 PM Dmitry Kozlyuk wrote:
>
> Previously, it was 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 t
Hi Dmitry,
> -Original Message-
> From: dev On Behalf Of Dmitry Kozlyuk
> Sent: Thursday, October 21, 2021 9:35 AM
> To: dev@dpdk.org
> Cc: Ori Kam ; NBU-Contact-Thomas Monjalon
> ;
> Ferruh Yigit ; Andrew Rybchenko
>
> Subject: [dpdk-dev] [PATCH v4 1/6] eth
Previously, it was 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 p
5 matches
Mail list logo
