From: Suanming Mou <suanmingm@mellanox.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] fix incorrect register usage in meter
Date: Thu, 23 Jan 2020 08:01:00 +0200 [thread overview]
Message-ID: <1579759262-189720-1-git-send-email-suanmingm@mellanox.com> (raw)
Flow with meter will split to three subflows, the prefix subflow with
meter action do the color, the meter subflow filter the packets, the
suffix subflow do all the left actions for packets pass the filter.
Both the color and the subflow match between prefix and suffix use the
register to store the tag.
For some of the NICs with meter color register share capability, it
only uses 8 LSB of the register for color, the left 24 MSB can be used
for flow id match between meter prefix subflow and suffix subflow.
Currently, one entire register is allocated for flow matching which
causes the NICs with limited registers don't have enough register for
other matching.
Add the meter color share capability checking to fix lacking of
registers issue.
Suanming Mou (2):
net/mlx5: support maximum id in id allocate
net/mlx5: fix incorrect register usage in meter
drivers/net/mlx5/mlx5.c | 19 +++++++++++----
drivers/net/mlx5/mlx5.h | 4 ++++
drivers/net/mlx5/mlx5_devx_cmds.c | 2 ++
drivers/net/mlx5/mlx5_flow.c | 49 ++++++++++++++++++++++++---------------
drivers/net/mlx5/mlx5_flow.h | 2 +-
drivers/net/mlx5/mlx5_flow_dv.c | 4 ++--
drivers/net/mlx5/mlx5_prm.h | 7 +++++-
7 files changed, 60 insertions(+), 27 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-01-23 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 6:01 Suanming Mou [this message]
2020-01-23 6:01 ` [dpdk-dev] [PATCH 1/2] net/mlx5: support maximum id in id allocate Suanming Mou
2020-01-26 21:44 ` Raslan Darawsheh
2020-01-23 6:01 ` [dpdk-dev] [PATCH 2/2] net/mlx5: fix incorrect register usage in meter Suanming Mou
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=1579759262-189720-1-git-send-email-suanmingm@mellanox.com \
--to=suanmingm@mellanox.com \
--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).