public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Cliff Burdick <cburdick@nvidia.com>
To: <dev@dpdk.org>
Cc: <anatoly.burakov@intel.com>
Subject: [PATCH v2 0/2] support dmabuf
Date: Tue, 3 Feb 2026 22:26:39 +0000	[thread overview]
Message-ID: <20260203222836.2862414-1-cburdick@nvidia.com> (raw)
In-Reply-To: <20260127174429.1504288-1-cburdick@nvidia.com>

Fixed since v1:
* Fixed issue with MSVC compilation
* Fixed style issues from code review

Add support for kernel dmabuf feature and integrate it in the mlx5 driver. 
This feature is needed to support GPUDirect on newer kernels.

Cliff Burdick (2):
  eal: support dmabuf
  common/mlx5: support dmabuf

 .mailmap                                      |   1 +
 doc/guides/rel_notes/release_26_03.rst        |   6 +
 drivers/common/mlx5/linux/meson.build         |   2 +
 drivers/common/mlx5/linux/mlx5_common_verbs.c |  48 ++++-
 drivers/common/mlx5/linux/mlx5_glue.c         |  19 ++
 drivers/common/mlx5/linux/mlx5_glue.h         |   3 +
 drivers/common/mlx5/mlx5_common.c             |  42 ++++-
 drivers/common/mlx5/mlx5_common_mr.c          | 113 +++++++++++-
 drivers/common/mlx5/mlx5_common_mr.h          |  17 +-
 drivers/common/mlx5/windows/mlx5_common_os.c  |   8 +-
 drivers/crypto/mlx5/mlx5_crypto.h             |   1 +
 drivers/crypto/mlx5/mlx5_crypto_gcm.c         |   3 +-
 lib/eal/common/eal_common_memory.c            | 165 +++++++++++++++++-
 lib/eal/common/eal_memalloc.h                 |  21 +++
 lib/eal/common/malloc_heap.c                  |  27 +++
 lib/eal/common/malloc_heap.h                  |   5 +
 lib/eal/include/rte_memory.h                  | 145 +++++++++++++++
 17 files changed, 612 insertions(+), 14 deletions(-)

-- 
2.52.0


  parent reply	other threads:[~2026-02-03 22:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 17:44 [PATCH 0/2] support dmabuf Cliff Burdick
2026-01-27 17:44 ` [PATCH 1/2] eal: " Cliff Burdick
2026-01-29  1:48   ` Stephen Hemminger
2026-01-29  1:51   ` Stephen Hemminger
2026-01-27 17:44 ` [PATCH 2/2] common/mlx5: " Cliff Burdick
2026-01-27 19:21   ` [REVIEW] " Stephen Hemminger
2026-01-28 14:30     ` David Marchand
2026-01-28 17:10       ` Stephen Hemminger
2026-01-28 17:43       ` Stephen Hemminger
2026-02-03 17:34     ` Cliff Burdick
2026-01-29  1:51   ` [PATCH 2/2] " Stephen Hemminger
2026-01-28  0:04 ` [PATCH 0/2] " Stephen Hemminger
2026-02-03 17:18   ` Cliff Burdick
2026-02-03 22:26 ` Cliff Burdick [this message]
2026-02-03 22:26   ` [PATCH v2 1/2] eal: " Cliff Burdick
2026-02-03 22:26   ` [PATCH v2 2/2] common/mlx5: " Cliff Burdick
2026-02-03 23:02   ` [PATCH v3 0/2] " Cliff Burdick
2026-02-03 23:02     ` [PATCH v3 1/2] eal: " Cliff Burdick
2026-02-03 23:02     ` [PATCH v3 2/2] common/mlx5: " Cliff Burdick
2026-02-04 15:50     ` [PATCH v4 0/2] " Cliff Burdick
2026-02-04 15:50       ` [PATCH v4 1/2] eal: " Cliff Burdick
2026-02-12 13:57         ` Burakov, Anatoly
2026-02-04 15:50       ` [PATCH v4 2/2] common/mlx5: " Cliff Burdick
2026-02-05 18:48       ` [PATCH v4 0/2] " Stephen Hemminger
2026-02-05 20:25         ` Cliff Burdick
2026-02-05 22:50           ` Stephen Hemminger
2026-03-31  3:15       ` Stephen Hemminger

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=20260203222836.2862414-1-cburdick@nvidia.com \
    --to=cburdick@nvidia.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    /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