DPDK patches and discussions
 help / color / mirror / Atom feed
From: Michael Baum <michaelba@nvidia.com>
To: <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	 Raslan Darawsheh <rasland@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>
Subject: [PATCH v3 0/2] net/mlx5: add random item support
Date: Thu, 14 Dec 2023 17:12:46 +0200	[thread overview]
Message-ID: <20231214151248.1654878-1-michaelba@nvidia.com> (raw)
In-Reply-To: <20231130164001.666702-1-michaelba@nvidia.com>

Add support for matching random value using the "rte_flow_item_random"
structure.

Depends-on: series-30553 ("ethdev: add random item support")

v2:
 - Rebase.
 - Move release notes to the new release file.

v3:
 - Fix typos in commit message and release notes.
 - Update limitations.


Erez Shitrit (1):
  net/mlx5/hws: add support for random number match

Michael Baum (1):
  net/mlx5: add random item support

 doc/guides/nics/features/mlx5.ini      |  1 +
 doc/guides/nics/mlx5.rst               |  9 +++++++
 doc/guides/rel_notes/release_24_03.rst |  3 +++
 drivers/net/mlx5/hws/mlx5dr_definer.c  | 33 ++++++++++++++++++++++++++
 drivers/net/mlx5/hws/mlx5dr_definer.h  |  8 ++++++-
 drivers/net/mlx5/mlx5_flow.h           |  3 +++
 drivers/net/mlx5/mlx5_flow_dv.c        |  5 ++++
 drivers/net/mlx5/mlx5_flow_hw.c        |  5 ++++
 8 files changed, 66 insertions(+), 1 deletion(-)

-- 
2.25.1


  parent reply	other threads:[~2023-12-14 15:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 10:35 [PATCH " Michael Baum
2023-08-22 10:35 ` [PATCH 1/2] net/mlx5/hws: add support for random number match Michael Baum
2023-10-29 15:55   ` Ori Kam
2023-08-22 10:36 ` [PATCH 2/2] net/mlx5: add random item support Michael Baum
2023-10-29 15:57   ` Ori Kam
2023-11-30 16:39 ` [PATCH v2 0/2] " Michael Baum
2023-11-30 16:40   ` [PATCH v2 1/2] net/mlx5/hws: add support for random number match Michael Baum
2023-12-08 19:31     ` Dariusz Sosnowski
2023-11-30 16:40   ` [PATCH v2 2/2] net/mlx5: add random item support Michael Baum
2023-12-08 19:58     ` Dariusz Sosnowski
2023-12-14 15:12   ` Michael Baum [this message]
2023-12-14 15:12     ` [PATCH v3 1/2] net/mlx5/hws: add support for random number match Michael Baum
2023-12-18  9:08       ` Dariusz Sosnowski
2023-12-14 15:12     ` [PATCH v3 2/2] net/mlx5: add random item support Michael Baum
2023-12-18  9:11       ` Dariusz Sosnowski
2023-12-25 10:24     ` [PATCH v4 0/2] " Michael Baum
2023-12-25 10:24       ` [PATCH v4 1/2] net/mlx5/hws: add support for random number match Michael Baum
2024-01-05  9:05         ` Dariusz Sosnowski
2023-12-25 10:24       ` [PATCH v4 2/2] net/mlx5: add random item support Michael Baum
2024-01-25 12:37       ` [PATCH v5 0/2] " Michael Baum
2024-01-25 12:37         ` [PATCH v5 1/2] net/mlx5/hws: add support for random number match Michael Baum
2024-01-25 12:37         ` [PATCH v5 2/2] net/mlx5: add random item support Michael Baum
2024-01-28  8:45         ` [PATCH v5 0/2] " 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=20231214151248.1654878-1-michaelba@nvidia.com \
    --to=michaelba@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=suanmingm@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).