From: Stephen Hemminger <stephen@networkplumber.org>
To: Gregory Etelson <getelson@nvidia.com>
Cc: <dev@dpdk.org>, <mkashani@nvidia.com>, <rasland@nvidia.com>,
"Elena Agostini" <eagostini@nvidia.com>
Subject: Re: [PATCH 1/9] gpu/cuda: add NVIDIA GPU H100
Date: Tue, 13 Jan 2026 09:36:55 -0800 [thread overview]
Message-ID: <20260113093655.025c8242@phoenix.local> (raw)
In-Reply-To: <20250915144137.54858-1-getelson@nvidia.com>
On Mon, 15 Sep 2025 17:41:28 +0300
Gregory Etelson <getelson@nvidia.com> wrote:
> From: Elena Agostini <eagostini@nvidia.com>
>
> Add support for new NVIDIA GPU H100.
>
> Signed-off-by: Elena Agostini <eagostini@nvidia.com>
> ---
In addition to Thomas's comments. AI code review also identified some problems.
Please fix and resubmit.
(Feels fun using AI to review Nvidia patches)...
## DPDK Patch Review: gpu/cuda NVIDIA GPU Device ID Series
**Series:** [PATCH 1/9] to [PATCH 9/9] - Adding NVIDIA GPU device IDs to CUDA driver
**Submitter:** Gregory Etelson (on behalf of Elena Agostini)
**Date:** Mon, 15 Sep 2025
---
### Overall Assessment
This series adds various NVIDIA GPU device IDs to the CUDA driver. While the technical changes are straightforward, there are several compliance issues with DPDK contribution guidelines.
---
### Patch-by-Patch Review
#### **Patch 1/9: `gpu/cuda: add NVIDIA GPU H100`**
| Check | Status | Notes |
|-------|--------|-------|
| Subject ≤60 chars | ✅ Pass | 31 characters |
| Lowercase after colon | ✅ Pass | |
| Component prefix | ✅ Pass | `gpu/cuda:` correct |
| Signed-off-by | ✅ Pass | Elena Agostini <eagostini@nvidia.com> |
| Commit body | ⚠️ Warning | Very minimal - "Add support for new NVIDIA GPU H100." |
**Verdict:** Acceptable, but body could be more descriptive.
---
#### **Patch 2/9: `gpu/cuda: new RoyB A100T GPU ID`**
| Check | Status | Notes |
|-------|--------|-------|
| Subject ≤60 chars | ✅ Pass | 33 characters |
| Subject style | ⚠️ Warning | "RoyB" - internal codename may not be meaningful to readers |
| **Commit body** | ❌ **Error** | **Missing description - only Signed-off-by present** |
| Signed-off-by | ✅ Pass | |
**Error (must fix):** Per AGENTS.md line 114: "Describe the issue being fixed or feature being added." This patch has no body text.
---
#### **Patch 3/9:** (inferred from context - adds more device IDs)
Similar pattern to other patches.
---
#### **Patch 4/9: `gpu/cuda: new Hopper GPU IDs`**
| Check | Status | Notes |
|-------|--------|-------|
| Subject | ✅ Pass | 27 characters |
| Commit body | ⚠️ Warning | Grammar: "Add **a** new NVIDIA Hopper GPU **IDs**" - article/noun disagreement |
| Signed-off-by | ✅ Pass | |
**Warning:** Should read either "Add new NVIDIA Hopper GPU IDs" or "Add a new NVIDIA Hopper GPU ID."
---
#### **Patch 5/9: `gpu/cuda: add new gpu hopper 80gb device id`**
| Check | Status | Notes |
|-------|--------|-------|
| Subject length | ✅ Pass | 47 characters |
| **Subject case** | ⚠️ **Warning** | "gpu" and "hopper" should likely be uppercase for consistency: "GPU" and "Hopper" |
| **Commit body mood** | ⚠️ **Warning** | "Added the new..." uses past tense. Should be imperative: "Add the new..." |
| Signed-off-by | ✅ Pass | |
**Warning (should fix):** Per AGENTS.md line 54: Mood should be "Imperative (instructions to codebase)."
---
#### **Patch 6/9:** (extends device IDs with A800, H800, L40, L4 series)
Major refactoring patch adding many device IDs. Code appears structurally sound.
---
#### **Patch 7/9: `gpu/cuda: extend NVIDIA GPU device ID list`**
| Check | Status | Notes |
|-------|--------|-------|
| Subject | ✅ Pass | 44 characters |
| **Signed-off-by** | ❌ **Error** | `Signed-off-by: eagostini <eagostini@nvidia.com>` - **uses username, not real name** |
| From: line | ❌ **Error** | `From: eagostini <eagostini@nvidia.com>` - same issue |
**Error (must fix):** Per AGENTS.md line 116: "Signed-off-by: present with **real name** and valid email" and line 168: "Tag format: Tag-name: **Full Name** <email@domain.com>."
Should be: `Signed-off-by: Elena Agostini <eagostini@nvidia.com>`
---
#### **Patch 8/9: `gpu/cuda: extend NVIDIA GPU device ID list`**
| Check | Status | Notes |
|-------|--------|-------|
| **Subject** | ⚠️ **Warning** | **Identical to Patch 7/9** - subjects should be unique/descriptive |
| **Signed-off-by** | ❌ **Error** | Same issue: `eagostini` instead of `Elena Agostini` |
| From: line | ❌ **Error** | Same issue |
**Warning:** Patches 7 and 8 have identical subjects. Per the spirit of AGENTS.md guidelines, subjects should meaningfully distinguish patches. Consider: "gpu/cuda: add Laptop and Embedded GPU IDs" for patch 8.
---
#### **Patch 9/9:** (extends list further with more Laptop/Embedded variants)
Similar issues to patches 7/8 regarding authorship formatting.
---
### Code Style Issues
#### **1. Duplicate Macro Values (Patch 5)**
```c
#define NVIDIA_GPU_HOPPER_GRACE (0x2342)
#define NVIDIA_GPU_H100_GH1_DEVICE_ID (0x2342)
```
Two different macros defined with the same PCI device ID `0x2342`. This appears intentional (same device, different names), but the `NVIDIA_GPU_HOPPER_GRACE` macro is later removed. The series should be consolidated to avoid this intermediate state breaking bisectability.
#### **2. Inconsistent Naming Convention**
The macro naming is inconsistent across the series:
- Some use `NVIDIA_GPU_*_DEVICE_ID` suffix
- Some use just `NVIDIA_*` (e.g., `NVIDIA_A40`, `NVIDIA_H100`)
- Some use `NVIDIA_RTX_*`
While not strictly an error, this inconsistency makes the code harder to maintain.
#### **3. Double Blank Lines (Patch 9)**
```c
+ },
+
+
+ {
```
Lines 2130-2131 show two consecutive blank lines, which violates typical formatting expectations.
#### **4. Missing Documentation Update**
Per AGENTS.md lines 646-650 and 658:
- "New drivers or subsystems must have release notes"
- "Update release notes in doc/guides/rel_notes/ for important changes"
Adding significant new GPU support (H100, H200, L40 series, etc.) should arguably have a release notes entry, though this is borderline for device ID additions.
---
### Summary of Required Fixes
| Severity | Issue | Patches Affected |
|----------|-------|------------------|
| **Error** | Missing commit body | 2/9 |
| **Error** | Signed-off-by uses alias, not real name | 7/9, 8/9, 9/9 |
| **Error** | From: uses alias, not real name | 7/9, 8/9, 9/9 |
| Warning | Past tense in commit body | 5/9 |
| Warning | Lowercase in subject where uppercase expected | 5/9 |
| Warning | Grammar error in body | 4/9 |
| Warning | Duplicate subject lines | 7/9 vs 8/9 |
| Warning | Double blank lines in code | 9/9 |
| Info | Inconsistent macro naming style | Multiple |
| Info | Consider release notes update | Series |
---
### Recommended Actions
1. **Patch 2/9:** Add a description to the commit body explaining what "RoyB A100T" refers to.
2. **Patches 7/9, 8/9, 9/9:** Change author and signoff from:
```
From: eagostini <eagostini@nvidia.com>
Signed-off-by: eagostini <eagostini@nvidia.com>
```
To:
```
From: Elena Agostini <eagostini@nvidia.com>
Signed-off-by: Elena Agostini <eagostini@nvidia.com>
```
3. **Patch 5/9:** Fix subject case and body tense:
- Subject: `gpu/cuda: add new GPU Hopper 80GB device ID`
- Body: "Add the new Hopper 80GB GPU device ID to the list."
4. **Patches 7 & 8:** Differentiate the subjects (e.g., one for datacenter GPUs, one for Laptop/Embedded).
5. **Patch 9:** Remove the double blank line in cuda.c.
prev parent reply other threads:[~2026-01-13 17:37 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
2026-01-13 17:36 ` Stephen Hemminger [this message]
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=20260113093655.025c8242@phoenix.local \
--to=stephen@networkplumber.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox