On Tue, 2018-09-25 at 14:34 +, Ananyev, Konstantin wrote:
> Hi Luca,
>
> >
> > On Sun, 2018-09-16 at 11:56 +0200, Thomas Monjalon wrote:
> > > 24/08/2018 18:47, Konstantin Ananyev:
> > > > If user specifies priority=0 for some of ACL rules
> > > > that can cause rte_acl_classify to return wro
Hi Luca,
>
> On Sun, 2018-09-16 at 11:56 +0200, Thomas Monjalon wrote:
> > 24/08/2018 18:47, Konstantin Ananyev:
> > > If user specifies priority=0 for some of ACL rules
> > > that can cause rte_acl_classify to return wrong results.
> > > The reason is that priority zero is used internally for no
25/09/2018 14:22, Luca Boccassi:
> On Sun, 2018-09-16 at 11:56 +0200, Thomas Monjalon wrote:
> > 24/08/2018 18:47, Konstantin Ananyev:
> > > If user specifies priority=0 for some of ACL rules
> > > that can cause rte_acl_classify to return wrong results.
> > > The reason is that priority zero is us
On Sun, 2018-09-16 at 11:56 +0200, Thomas Monjalon wrote:
> 24/08/2018 18:47, Konstantin Ananyev:
> > If user specifies priority=0 for some of ACL rules
> > that can cause rte_acl_classify to return wrong results.
> > The reason is that priority zero is used internally for no-match
> > nodes.
> > S
24/08/2018 18:47, Konstantin Ananyev:
> If user specifies priority=0 for some of ACL rules
> that can cause rte_acl_classify to return wrong results.
> The reason is that priority zero is used internally for no-match nodes.
> See more details at: https://bugs.dpdk.org/show_bug.cgi?id=79.
> The simp
If user specifies priority=0 for some of ACL rules
that can cause rte_acl_classify to return wrong results.
The reason is that priority zero is used internally for no-match nodes.
See more details at: https://bugs.dpdk.org/show_bug.cgi?id=79.
The simplest way to overcome the issue is just not allow
6 matches
Mail list logo