DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shun Hao <shunh@nvidia.com>
To: <viacheslavo@nvidia.com>, <matan@nvidia.com>, <orika@nvidia.com>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [PATCH v1 0/2] Fix src port match in meter hierarchy
Date: Tue, 8 Nov 2022 12:03:59 +0200	[thread overview]
Message-ID: <20221108100401.878296-1-shunh@nvidia.com> (raw)

In meter hierarchy, if policy flow contains modify_field or port_id
action, a src port matching will be added to determine the position of
meter in action list.

Currently the src port is static, using the port id policy belongs to.
This patch set enables creation of multiple policy flows using src port
from user flow dynamically to match different src port, so the meter
hierarchy can always be used by different src ports.

Shun Hao (2):
  net/mlx5: fix meter hierarchy with modify header
  net/mlx5: fix meter policy with port ID destination

 doc/guides/nics/mlx5.rst        |   3 +
 drivers/net/mlx5/mlx5.h         |   8 +-
 drivers/net/mlx5/mlx5_flow.c    |   2 +-
 drivers/net/mlx5/mlx5_flow_dv.c | 126 +++++++++++++++++---------------
 4 files changed, 77 insertions(+), 62 deletions(-)

-- 
2.20.0


             reply	other threads:[~2022-11-08 10:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 10:03 Shun Hao [this message]
2022-11-08 10:04 ` [PATCH v1 1/2] net/mlx5: fix meter hierarchy with modify header Shun Hao
2022-11-08 10:04 ` [PATCH v1 2/2] net/mlx5: fix meter policy with port ID destination Shun Hao
2022-11-08 17:35 ` [PATCH v1 0/2] Fix src port match in meter hierarchy 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=20221108100401.878296-1-shunh@nvidia.com \
    --to=shunh@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=viacheslavo@nvidia.com \
    /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).