> > > However, as more and more applications are offloading some or all > > > logic and action to the HW, there is a need to check the packet > > > integrity so the right decision can be taken. > > > > > > The application logic can be positive meaning if the packet is > > > valid jump / do actions, or negative if packet is not valid > > > jump to SW / do actions (like drop) a, and add default flow > > > (match all in low priority) that will direct the miss packet > > > to the miss path. > > > > Unless I missed it, > > How do you specify the negative case? > > Can you provide an example as well? > > > You can use negative case by setting the bit to zero and the mask bit to 1: > This example was taken from the testpmd patch: > flow create 0 ingress pattern integrity value mask 1 value spec 0 / end > actions queue index 0 / end > it matches all invalid packets and forward it to the application. Thanks Ori.
> > > > > > Signed-off-by: Ori Kam <or...@nvidia.com> Acked-by: Ajit Khaparde <ajit.khapa...@broadcom.com> > > > --- > > > doc/guides/prog_guide/rte_flow.rst | 20 +++++++++++ > > > doc/guides/rel_notes/release_21_05.rst | 5 +++ > > > lib/librte_ethdev/rte_flow.h | 49 ++++++++++++++++++++++++++ > > > 3 files changed, 74 insertions(+)
