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 0/4] net/mlx5: some unrelated fixes and improvements
Date: Tue, 16 Apr 2024 18:30:50 +0300	[thread overview]
Message-ID: <20240416153054.3216706-1-michaelba@nvidia.com> (raw)

This patch-set groups some unrelated fixes and improvements in MLX5 PMD
code.

Michael Baum (4):
  net/mlx5: fix secondary process port close
  net/mlx5/hws: fix GENEVE option class partial mask
  net/mlx5/hws: add fragment packet ID matching support
  net/mlx5/hws: remove table type DONTCARE

 drivers/net/mlx5/hws/mlx5dr.h         |  1 -
 drivers/net/mlx5/hws/mlx5dr_definer.c | 47 +++++++++++++++------------
 drivers/net/mlx5/hws/mlx5dr_definer.h |  2 ++
 drivers/net/mlx5/mlx5.c               | 15 +++++----
 drivers/net/mlx5/mlx5_flow.h          |  2 +-
 5 files changed, 37 insertions(+), 30 deletions(-)

-- 
2.25.1


             reply	other threads:[~2024-04-16 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 15:30 Michael Baum [this message]
2024-04-16 15:30 ` [PATCH 1/4] net/mlx5: fix secondary process port close Michael Baum
2024-04-16 15:30 ` [PATCH 2/4] net/mlx5/hws: fix GENEVE option class partial mask Michael Baum
2024-04-16 15:30 ` [PATCH 3/4] net/mlx5/hws: add fragment packet ID matching support Michael Baum
2024-04-16 15:30 ` [PATCH 4/4] net/mlx5/hws: remove table type DONTCARE Michael Baum
2024-04-29  7:46 ` [PATCH 0/4] net/mlx5: some unrelated fixes and improvements 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=20240416153054.3216706-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).