Hi,
On 13/10/2021 04:25, Alexander Kozyrev wrote:
From: Ivan Malov On Wednesday, October 6, 2021 13:25
On 06/10/2021 07:48, Alexander Kozyrev wrote:
Treating every single flow rule as a completely independent and separate
entity negatively impacts the flow rules insertion rate. Oftentimes in a
> From: Ajit Khaparde On Tuesday, October 12, 2021
> 22:27
> To: Alexander Kozyrev
> >
> > > From: Ivan Malov On Wednesday, October 6,
> 2021 13:25
> > > On 06/10/2021 07:48, Alexander Kozyrev wrote:
> > > > Treating every single flow rule as a completely independent and
> separate
> > > > enti
On Tue, Oct 12, 2021 at 6:25 PM Alexander Kozyrev wrote:
>
> > From: Ivan Malov On Wednesday, October 6, 2021
> > 13:25
> > On 06/10/2021 07:48, Alexander Kozyrev wrote:
> > > Treating every single flow rule as a completely independent and separate
> > > entity negatively impacts the flow rules
> From: Ivan Malov On Wednesday, October 6, 2021 13:25
> On 06/10/2021 07:48, Alexander Kozyrev wrote:
> > Treating every single flow rule as a completely independent and separate
> > entity negatively impacts the flow rules insertion rate. Oftentimes in an
> > application, many flow rules share a
Hi,
On 06/10/2021 07:48, Alexander Kozyrev wrote:
Treating every single flow rule as a completely independent and separate
entity negatively impacts the flow rules insertion rate. Oftentimes in an
application, many flow rules share a common structure (the same item mask
and/or action list) so th
Treating every single flow rule as a completely independent and separate
entity negatively impacts the flow rules insertion rate. Oftentimes in an
application, many flow rules share a common structure (the same item mask
and/or action list) so they can be grouped and classified together.
This knowl
6 matches
Mail list logo
