21/02/2022 15:53, Andrew Rybchenko:
> On 2/21/22 15:53, Ori Kam wrote:
> > From: Andrew Rybchenko
> +/**
> + * @warning
> + * @b EXPERIMENTAL: this API may change without prior notice.
> + *
> + * Get information about flow engine resources.
> + *
> + * @param po
On 2/21/22 15:53, Ori Kam wrote:
Hi Andrew and Alexander,
-Original Message-
From: Andrew Rybchenko
Sent: Monday, February 21, 2022 11:53 AM
Subject: Re: [PATCH v8 01/11] ethdev: introduce flow engine configuration
On 2/21/22 12:47, Andrew Rybchenko wrote:
On 2/20/22 06:43
On Monday, February 21, 2022 7:54 Ori Kam wrote:
> Hi Andrew and Alexander,
>
> > -Original Message-
> > From: Andrew Rybchenko
> > Sent: Monday, February 21, 2022 11:53 AM
> > Subject: Re: [PATCH v8 01/11] ethdev: introduce flow engine configuration
&g
Hi Andrew and Alexander,
> -Original Message-
> From: Andrew Rybchenko
> Sent: Monday, February 21, 2022 11:53 AM
> Subject: Re: [PATCH v8 01/11] ethdev: introduce flow engine configuration
>
> On 2/21/22 12:47, Andrew Rybchenko wrote:
> > On 2/20/22 06:43,
On 2/21/22 12:47, Andrew Rybchenko wrote:
On 2/20/22 06:43, Alexander Kozyrev wrote:
The flow rules creation/destruction at a large scale incurs a performance
penalty and may negatively impact the packet processing when used
as part of the datapath logic. This is mainly because software/hardware
On 2/20/22 06:43, Alexander Kozyrev wrote:
The flow rules creation/destruction at a large scale incurs a performance
penalty and may negatively impact the packet processing when used
as part of the datapath logic. This is mainly because software/hardware
resources are allocated and prepared durin
The flow rules creation/destruction at a large scale incurs a performance
penalty and may negatively impact the packet processing when used
as part of the datapath logic. This is mainly because software/hardware
resources are allocated and prepared during the flow rule creation.
In order to optimi
7 matches
Mail list logo
