DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alexander Kozyrev <akozyrev@nvidia.com>
To: <dev@dpdk.org>
Cc: <rasland@nvidia.com>, <viacheslavo@nvidia.com>,
	<matan@nvidia.com>, <hamdani@nvidia.com>, <valex@nvidia.com>,
	<dsosnowski@nvidia.com>, <orika@nvidia.com>, <bingz@nvidia.com>,
	<suanmingm@nvidia.com>
Subject: [PATCH v3 0/5] jump to table index support in mlx5
Date: Thu, 24 Oct 2024 18:41:24 +0300	[thread overview]
Message-ID: <20241024154351.1743447-1-akozyrev@nvidia.com> (raw)

Support the new Flow API JUMP_TO_TABLE_INDEX action in mlx5.

Seried-acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>

Alexander Kozyrev (3):
  net/mlx5: create array ste matcher
  net/mlx5: add flow rule insertion by index with pattern
  net/mlx5: implement jump to table index action

Hamdan Igbaria (2):
  net/mlx5/hws: introduce new matcher type
  net/mlx5/hws: introduce jump to matcher action

 doc/guides/nics/features/mlx5.ini             |   1 +
 doc/guides/prog_guide/ethdev/flow_offload.rst |  24 +
 doc/guides/rel_notes/release_24_11.rst        |   3 +
 drivers/net/mlx5/hws/mlx5dr.h                 |  42 +-
 drivers/net/mlx5/hws/mlx5dr_action.c          |  87 +++-
 drivers/net/mlx5/hws/mlx5dr_action.h          |   3 +
 drivers/net/mlx5/hws/mlx5dr_debug.c           |  13 +-
 drivers/net/mlx5/hws/mlx5dr_matcher.c         |  58 ++-
 drivers/net/mlx5/hws/mlx5dr_matcher.h         |   6 +
 drivers/net/mlx5/hws/mlx5dr_rule.c            |   2 +-
 drivers/net/mlx5/hws/mlx5dr_table.c           |  61 ++-
 drivers/net/mlx5/hws/mlx5dr_table.h           |   8 +-
 drivers/net/mlx5/mlx5_flow.h                  |   8 +-
 drivers/net/mlx5/mlx5_flow_hw.c               | 435 ++++++++++--------
 14 files changed, 519 insertions(+), 232 deletions(-)

-- 
2.43.5


             reply	other threads:[~2024-10-24 15:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 15:41 Alexander Kozyrev [this message]
2024-10-24 15:41 ` [PATCH v3 1/5] net/mlx5/hws: introduce new matcher type Alexander Kozyrev
2024-10-24 15:41 ` [PATCH v3 2/5] net/mlx5/hws: introduce jump to matcher action Alexander Kozyrev
2024-10-24 15:41 ` [PATCH v3 3/5] net/mlx5: create array ste matcher Alexander Kozyrev
2024-10-24 15:41 ` [PATCH v3 4/5] net/mlx5: add flow rule insertion by index with pattern Alexander Kozyrev
2024-10-24 15:41 ` [PATCH v3 5/5] net/mlx5: implement jump to table index action Alexander Kozyrev
2024-10-24 17:50 ` [PATCH v4 0/5] jump to table index support in mlx5 Alexander Kozyrev
2024-10-24 17:50   ` [PATCH v4 1/5] net/mlx5/hws: introduce new matcher type Alexander Kozyrev
2024-10-24 17:50   ` [PATCH v4 2/5] net/mlx5/hws: introduce jump to matcher action Alexander Kozyrev
2024-10-24 17:50   ` [PATCH v4 3/5] net/mlx5: create array ste matcher Alexander Kozyrev
2024-10-24 17:50   ` [PATCH v4 4/5] net/mlx5: add flow rule insertion by index with pattern Alexander Kozyrev
2024-10-24 17:50   ` [PATCH v4 5/5] net/mlx5: implement jump to table index action Alexander Kozyrev

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=20241024154351.1743447-1-akozyrev@nvidia.com \
    --to=akozyrev@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=hamdani@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --cc=valex@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).