From: Thomas Monjalon <thomas@monjalon.net>
To: Bing Zhao <bingz@nvidia.com>,
Elena Agostini <eagostini@nvidia.com>,
Gregory Etelson <getelson@nvidia.com>
Cc: dev@dpdk.org, mkashani@nvidia.com, rasland@nvidia.com
Subject: Re: [PATCH 9/9] gpu/cuda: support CUDA 13 building
Date: Fri, 05 Dec 2025 09:55:33 +0100 [thread overview]
Message-ID: <13930065.uLZWGnKmhe@thomas> (raw)
In-Reply-To: <4771590.kQq0lBPeGt@thomas>
17/09/2025 12:06, Thomas Monjalon:
> 15/09/2025 16:41, Gregory Etelson:
> > From: Bing Zhao <bingz@nvidia.com>
> >
> > The API name and prototype have been changed in the new CUDA, this
> > commit will ensure the compatibility with different versions.
> [...]
> > /* CUDA Driver functions loaded with cuGetProcAddress for versioning */
> > +#if defined(CUDA_VERSION) && (CUDA_VERSION >= 13000)
> > +static PFN_cuGetErrorString_v6000 pfn_cuGetErrorString;
> > +static PFN_cuGetErrorName_v6000 pfn_cuGetErrorName;
> > +static PFN_cuPointerSetAttribute_v6000 pfn_cuPointerSetAttribute;
> > +static PFN_cuDeviceGetAttribute_v2000 pfn_cuDeviceGetAttribute;
> > +static PFN_cuDeviceGetByPCIBusId_v4010 pfn_cuDeviceGetByPCIBusId;
> > +static PFN_cuDevicePrimaryCtxRetain_v7000 pfn_cuDevicePrimaryCtxRetain;
> > +static PFN_cuDevicePrimaryCtxRelease_v11000 pfn_cuDevicePrimaryCtxRelease;
> > +static PFN_cuDeviceTotalMem_v3020 pfn_cuDeviceTotalMem;
> > +static PFN_cuDeviceGetName_v2000 pfn_cuDeviceGetName;
> > +static PFN_cuCtxGetApiVersion_v3020 pfn_cuCtxGetApiVersion;
> > +static PFN_cuCtxSetCurrent_v4000 pfn_cuCtxSetCurrent;
> > +static PFN_cuCtxGetCurrent_v4000 pfn_cuCtxGetCurrent;
> > +static PFN_cuCtxGetDevice_v2000 pfn_cuCtxGetDevice;
> > +static PFN_cuCtxGetExecAffinity_v11040 pfn_cuCtxGetExecAffinity;
> > +static PFN_cuMemAlloc_v3020 pfn_cuMemAlloc;
> > +static PFN_cuMemFree_v3020 pfn_cuMemFree;
> > +static PFN_cuMemHostRegister_v6050 pfn_cuMemHostRegister;
> > +static PFN_cuMemHostUnregister_v4000 pfn_cuMemHostUnregister;
> > +static PFN_cuMemHostGetDevicePointer_v3020 pfn_cuMemHostGetDevicePointer;
> > +static PFN_cuFlushGPUDirectRDMAWrites_v11030 pfn_cuFlushGPUDirectRDMAWrites;
> > +#else
> > static PFN_cuGetErrorString pfn_cuGetErrorString;
> > static PFN_cuGetErrorName pfn_cuGetErrorName;
>
> What is the logic here?
> The old version keeps its original name, and new versions have a suffix?
> Why not use the old version?
> What will happen with next versions?
Looks like we cannot do better than this versioning
when using cuGetProcAddress to avoid linking CUDA.
Applied
next prev parent reply other threads:[~2025-12-05 8:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 14:41 [PATCH 1/9] gpu/cuda: add NVIDIA GPU H100 Gregory Etelson
2025-09-15 14:41 ` [PATCH 2/9] gpu/cuda: new RoyB A100T GPU ID Gregory Etelson
2025-09-15 14:41 ` [PATCH 3/9] [gpu/cuda] New NVIDIA GPU Hopper device ID on Grace Gregory Etelson
2025-09-15 14:41 ` [PATCH 4/9] gpu/cuda: add new Hopper GPU IDs Gregory Etelson
2025-09-15 14:41 ` [PATCH 5/9] gpu/cuda: add new gpu hopper 80gb device id Gregory Etelson
2025-09-15 14:41 ` [PATCH 6/9] gpu/cuda: more gpu ID for h100 and l40 Gregory Etelson
2026-03-04 13:17 ` Maurice Green
2025-09-15 14:41 ` [PATCH 7/9] gpu/cuda: extend NVIDIA GPU device ID list Gregory Etelson
2025-09-17 10:03 ` Thomas Monjalon
2026-03-04 13:28 ` Maurice Green
2026-03-04 14:06 ` Thomas Monjalon
2026-03-04 22:50 ` Maurice Green
2026-03-05 13:59 ` Thomas Monjalon
2025-09-15 14:41 ` [PATCH 8/9] " Gregory Etelson
2025-09-15 14:41 ` [PATCH 9/9] gpu/cuda: support CUDA 13 building Gregory Etelson
2025-09-17 10:06 ` Thomas Monjalon
2025-12-05 8:55 ` Thomas Monjalon [this message]
2026-01-13 17:36 ` [PATCH 1/9] gpu/cuda: add NVIDIA GPU H100 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=13930065.uLZWGnKmhe@thomas \
--to=thomas@monjalon.net \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=eagostini@nvidia.com \
--cc=getelson@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=rasland@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.