Re: rte-flow: unmatched ingress traffic default action

["Robin Jarry" <rjarry@redhat.com>]

Hi Ori,

Ori Kam, Oct 18, 2022 at 09:41:
> > Should I read "general expectation" as a simple recommendation or is
> > it a requirement from the RTE flow API?
>
> I think the wording in the doc should change since it is not clear. So
> let me clarify it.
>
> The idea of isolated mode is that the DPDK application will only get
> traffic that the application actively requested.
>
> When working in isolated mode (relevant only for ingress traffic), the
> DPDK port can only receive traffic that the application configured
> a matching rule. If no matching rule was set the packet is moved to
> the next application/kernel or dropped if no such application/kernel
> exists.

Oh I was not clear enough. I *don't* use the isolated mode. The "general
expectation" I am referring to seems to be in the non-isolated mode.

> > Can I expect *all* ingress traffic *not* matching ether_type=0x1234
> > to be redirected to queues 0 and 1 following the default RSS
> > algorithm?
>
> No, all traffic not matching the rule will be moved to the kernel in
> case of a bifurcated driver, MLX5 for example, or dropped assuming
> there is no other application with a matching rule.

This is also in regular (non-isolated) mode?

Thanks!

Robin