From: Thomas Monjalon <thomas@monjalon.net>
To: Maurice Green <maurice.green@mauricegreenjr.com>
Cc: dev@dpdk.org, eagostini@nvidia.com, getelson@nvidia.com,
mkashani@nvidia.com, rasland@nvidia.com
Subject: Re: [PATCH 7/9] gpu/cuda: extend NVIDIA GPU device ID list
Date: Thu, 05 Mar 2026 14:59:41 +0100 [thread overview]
Message-ID: <6412176.lOV4Wx5bFT@thomas> (raw)
In-Reply-To: <20260304225051.26238-1-maurice.green@mauricegreenjr.com>
04/03/2026 23:50, Maurice Green:
> > +#define NVIDIA_GPU_GH100 0x2335 /* H200 SXM 141GB */
> >
> > As you can see it requires knowledge to get the right name for each ID.
> > Not everything is in https://pci-ids.ucw.cz/
> > https://github.com/NVIDIA/open-gpu-kernel-modules is a good source but not perfect as well.
>
> Right, the naming is a little tricky since neither source is fully complete.
> I wrote a sync script that cross-references the PCI ID DB and OKM repo to
> construct unique macro names. For the few entries with totally identical
> descriptions across both sources, the device ID is appended as a fallback.
> Here is an example for the GH100 family:
>
> #define NVIDIA_GPU_GH100_H20 0x2329 /* H20 */
> #define NVIDIA_GPU_GH100_H20_HBM3E 0x232c /* H20 HBM3e */
> #define NVIDIA_GPU_GH100_H100_SXM5_80GB 0x2330 /* H100 SXM5 80GB */
> #define NVIDIA_GPU_GH100_H100_PCIE 0x2331 /* H100 PCIe */
> #define NVIDIA_GPU_GH100_H200_SXM_141GB 0x2335 /* H200 SXM 141GB */
> #define NVIDIA_GPU_GH100_H100 0x2336 /* H100 */
That's interesting.
How do you suggest to fill the gaps in these databases?
next prev parent reply other threads:[~2026-03-05 13:59 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 [this message]
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
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=6412176.lOV4Wx5bFT@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=eagostini@nvidia.com \
--cc=getelson@nvidia.com \
--cc=maurice.green@mauricegreenjr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox