DPDK patches and discussions
 help / color / mirror / Atom feed
From: <michaelba@nvidia.com>
To: <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Michael Baum <michaelba@oss.nvidia.com>
Subject: [dpdk-dev] [PATCH 0/6] mlx5: some UAR fixes
Date: Wed, 3 Nov 2021 20:35:07 +0200	[thread overview]
Message-ID: <20211103183513.104503-1-michaelba@nvidia.com> (raw)

From: Michael Baum <michaelba@oss.nvidia.com>

Some different fixes around User Access Memory object.

Michael Baum (6):
  crypto/mlx5: fix invalid memory access in probing
  common/mlx5: fix redundant code in UAR allocation
  common/mlx5: fix UAR allocation diagnostics messages
  common/mlx5: fix doorbell mapping configuration
  net/mlx5: remove duplicated reference of the TxQ doorbell
  common/mlx5: fix post doorbell barrier

 drivers/common/mlx5/mlx5_common.c        | 101 ++++++++----
 drivers/common/mlx5/mlx5_common.h        |  91 ++++++++++-
 drivers/common/mlx5/mlx5_common_defs.h   |   8 +
 drivers/common/mlx5/version.map          |   5 +-
 drivers/compress/mlx5/mlx5_compress.c    |  69 ++------
 drivers/crypto/mlx5/mlx5_crypto.c        |  72 ++-------
 drivers/crypto/mlx5/mlx5_crypto.h        |   6 +-
 drivers/net/mlx5/linux/mlx5_verbs.c      |  48 +++++-
 drivers/net/mlx5/mlx5.c                  | 195 +++++------------------
 drivers/net/mlx5/mlx5.h                  |  12 +-
 drivers/net/mlx5/mlx5_defs.h             |   8 -
 drivers/net/mlx5/mlx5_devx.c             |  24 +--
 drivers/net/mlx5/mlx5_flow_aso.c         |  81 +++++-----
 drivers/net/mlx5/mlx5_rx.h               |   6 +-
 drivers/net/mlx5/mlx5_rxq.c              |  11 +-
 drivers/net/mlx5/mlx5_tx.h               | 103 ++----------
 drivers/net/mlx5/mlx5_txpp.c             |  36 ++---
 drivers/net/mlx5/mlx5_txq.c              |  79 ++-------
 drivers/regex/mlx5/mlx5_regex.c          |  17 +-
 drivers/regex/mlx5/mlx5_regex.h          |   2 +-
 drivers/regex/mlx5/mlx5_regex_control.c  |   4 +-
 drivers/regex/mlx5/mlx5_regex_fastpath.c |  26 ++-
 drivers/vdpa/mlx5/mlx5_vdpa.h            |   2 +-
 drivers/vdpa/mlx5/mlx5_vdpa_event.c      |  33 +---
 24 files changed, 390 insertions(+), 649 deletions(-)

-- 
2.25.1


             reply	other threads:[~2021-11-03 18:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 18:35 michaelba [this message]
2021-11-03 18:35 ` [dpdk-dev] [PATCH 1/6] crypto/mlx5: fix invalid memory access in probing michaelba
2021-11-03 18:35 ` [dpdk-dev] [PATCH 2/6] common/mlx5: fix redundant code in UAR allocation michaelba
2021-11-03 18:35 ` [dpdk-dev] [PATCH 3/6] common/mlx5: fix UAR allocation diagnostics messages michaelba
2021-11-03 18:35 ` [dpdk-dev] [PATCH 4/6] common/mlx5: fix doorbell mapping configuration michaelba
2021-11-03 18:35 ` [dpdk-dev] [PATCH 5/6] net/mlx5: remove duplicated reference of the TxQ doorbell michaelba
2021-11-03 18:35 ` [dpdk-dev] [PATCH 6/6] common/mlx5: fix post doorbell barrier michaelba
2021-11-07 15:23 ` [dpdk-dev] [PATCH 0/6] mlx5: some UAR fixes Thomas Monjalon

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=20211103183513.104503-1-michaelba@nvidia.com \
    --to=michaelba@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=michaelba@oss.nvidia.com \
    --cc=thomas@monjalon.net \
    /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).