DPDK patches and discussions
 help / color / mirror / Atom feed
From: Carasec Elena <xcaras00@stud.fit.vutbr.cz>
To: dev@dpdk.org
Subject: [dpdk-dev] mlx5: match broadcast and multicast packets using flows
Date: Fri, 02 Oct 2020 12:53:18 +0200	[thread overview]
Message-ID: <f8a7bfdc5ebd83217edb17b9ce256e8e@stud.fit.vutbr.cz> (raw)

Hello,

I am trying to create flow rules that will match broadcast and multicast 
packets using testpmd
on mlx5 'MT27800 Family [ConnectX-5] 1017'. However, after creating the 
following rules, they do not match any packets.

My testpmd script is:

port stop all
port config all rss none
set promisc 0 on
set allmulti 0 on
port start all
set link-up port all
flow create 0 group 0 ingress pattern eth dst is ff:ff:ff:ff:ff:ff / 
ipv4 / end actions mark id 1 / count / queue index 1 / end
flow create 0 group 0 ingress pattern eth dst is ff:ff:ff:ff:ff:ff / 
ipv6 / end actions mark id 1 / count / queue index 1 / end
flow create 0 group 0 ingress pattern eth dst spec 01:00:00:00:00:00 dst 
mask 01:00:00:00:00:00 / ipv4 / end actions mark id 2 / count / queue 
index 2 / end
flow create 0 group 0 ingress pattern eth dst spec 01:00:00:00:00:00 dst 
mask 01:00:00:00:00:00 / ipv6 / end actions mark id 2 / count / queue 
index 2 / end
flow create 0 group 0 priority 1 ingress pattern end actions queue index 
3 / count / end
start

All the packets will match the last rule.

Also, creating only the rule
flow create 0 group 0 ingress pattern eth dst spec 01:00:00:00:00:00 dst 
mask 01:00:00:00:00:00 / end actions mark id 2 / count / queue index 2 / 
end
fails with error "port_flow_complain(): Caught PMD error type 1 (cause 
unspecified): hardware refuses to create flow: File exists"

What may be the reason of it? Is there another way to match broadcast 
and multicast packets using flow?

Thank you.
Elena Carasec

             reply	other threads:[~2020-10-02 10:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 10:53 Carasec Elena [this message]
2020-11-13 15:18 ` Slava Ovsiienko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f8a7bfdc5ebd83217edb17b9ce256e8e@stud.fit.vutbr.cz \
    --to=xcaras00@stud.fit.vutbr.cz \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).