DPDK usage discussions
 help / color / mirror / Atom feed
From: Georgios Katsikas <katsikas.gp@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Problem installing rules with counters on MLX5
Date: Thu, 11 Oct 2018 15:00:41 +0300	[thread overview]
Message-ID: <CAN9HtFD2BOEcGnvoghWJRJ=yUtyU2a4xNtvzMpYpnHSm6YszPg@mail.gmail.com> (raw)

Dear all,

I am trying to install 3 simple rules (to match ICMP, TCP, and UDP flows)
on a Mellanox ConnectX-5 100 GbE NIC using DPDK's flow API.
The rules are as follows:

   1. flow create 0 ingress pattern eth type is 2048 / ipv4 proto spec 1
   proto mask 0x0 / end actions queue index 0 / count / end
   2. flow create 0 ingress pattern eth type is 2048 / ipv4 proto spec 6
   proto mask 0x0 / end actions queue index 0 / count / end
   3. flow create 0 ingress pattern eth type is 2048 / ipv4 proto spec 17
   proto mask 0x0 / end actions queue index 0 / count / end

Only the first rule gets properly installed. The remaining 2 rules throw
the following error:
Caught error type 1 (cause unspecified): hardware refuses to create flow

If I try to incorporate 'count identifier <index> shared 0', I still get
error (with or without shared).
If I try to install the same rules without action count, then everything
works as expected.
Action count on rules that match src/dst IP addresses works fine.
Could you please shed some light on this?

I am using DPDK 18.08 with Mellanox OFED 4.4-2.0.7.0 (latest).

Thanks,
Georgios

             reply	other threads:[~2018-10-11 12:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 12:00 Georgios Katsikas [this message]
2018-10-11 12:16 ` Raslan Darawsheh
2018-10-11 12:21   ` Georgios Katsikas
2018-10-12 16:11   ` Cliff Burdick
2018-10-14  7:43     ` Raslan Darawsheh
2018-10-14 13:26       ` Cliff Burdick
2018-10-15 11:02         ` Raslan Darawsheh

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='CAN9HtFD2BOEcGnvoghWJRJ=yUtyU2a4xNtvzMpYpnHSm6YszPg@mail.gmail.com' \
    --to=katsikas.gp@gmail.com \
    --cc=users@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).