[PATCH v4 0/2] support dmabuf

Cliff Burdick cburdick at nvidia.com
Thu Feb 5 21:25:01 CET 2026


> -----Original Message-----
> From: Stephen Hemminger <stephen at networkplumber.org>
> Sent: Thursday, February 5, 2026 10:49 AM
> To: Cliff Burdick <cburdick at nvidia.com>
> Cc: dev at dpdk.org; anatoly.burakov at intel.com
> Subject: Re: [PATCH v4 0/2] support dmabuf]()
> 
> External email: Use caution opening links or attachments
> 
> On Wed, 4 Feb 2026 15:50:07 +0000
> Cliff Burdick <cburdick at nvidia.com> wrote:
> 
> > Fixes since v3:
> > * Fixed version in RTE_EXPORT_EXPERIMENTAL_SYMBOL
> > 
> > Add support for kernel dmabuf feature and integrate it in the mlx5 driver.
> > This feature is needed to support GPUDirect on newer kernels.
> > 
> > I apologize for all the patches. Still trying to learn how to submit these.
> > 
> > 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(-)
> > 
> Any new library like this needs standalone tests so that it gets covered in CI etc.

I did not see any existing GPU tests, and this would require a GPU to test along with a 5.15+ Linux kernel. Do those systems exist in the test infrastructure?


More information about the dev mailing list