public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Maayan Kashani <mkashani@nvidia.com>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>, <stable@dpdk.org>,
	"Dariusz Sosnowski" <dsosnowski@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Subject: Re: [PATCH 1/4] drivers: fix flow devarg handling for future HW
Date: Mon, 12 Jan 2026 17:20:30 -0800	[thread overview]
Message-ID: <20260112172030.1ecf0a1a@phoenix.local> (raw)
In-Reply-To: <20260112092439.14843-2-mkashani@nvidia.com>

On Mon, 12 Jan 2026 11:24:35 +0200
Maayan Kashani <mkashani@nvidia.com> wrote:

> SWS (software steering) will be disabled on future hardware generations.
> This fix should check for SWS capability bits and return relevant error.
> Update the defaults for the dv_flow_en and allow_duplicate_pattern
> devargs accordingly.
> 
> - Default dv_flow_en devarg value will be chosen based on whether
>   NIC supports SW steering and/or HW steering.
> - If DV flow is not supported and allow_duplicate_pattern is
>   set by the user, forcibly disable it and emit a clear log message.
> 
> This change improves reliability by ensuring only valid
> configurations are applied, and provides clear feedback to
> the user when fallbacks are triggered.
> 
> Fixes: 1b55eeb7b76f ("common/mlx5: add ConnectX-9 SuperNIC")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
> ---

Experimental AI review was generally happy with this patch.

The only thing it squawked about was:



## Revised Patch Review: `[PATCH 1/4] drivers: fix flow devarg handling for future HW`

### Commit Message Review

| Check | Status | Notes |
|-------|--------|-------|
| Subject ≤60 chars | ✅ Pass | 47 characters |
| Imperative mood | ✅ Pass | "fix" is imperative |
| No trailing period | ✅ Pass | |
| Lowercase after colon | ✅ Pass | |
| Body line wrap ≤75 chars | ✅ Pass | |
| Body doesn't start with "It" | ✅ Pass | |
| Signed-off-by present | ✅ Pass | |
| Fixes tag format | ✅ Pass | 12-char SHA with quoted subject |
| Cc: stable@dpdk.org | ✅ Pass | |
| Tag order | ✅ Pass | |

#### ⚠️ Warning: Subject Prefix
`drivers:` is generic. Since this primarily affects `net/mlx5` with supporting changes in `common/mlx5`, consider:
- **Suggested**: `net/mlx5: fix flow devarg handling for future HW`

---

### Code Style Review

| Check | Status |
|-------|--------|
| Line length ≤100 chars | ✅ Pass |
| Explicit NULL comparisons | ✅ Pass |
| Comment formatting | ✅ Pass |
| Function naming | ✅ Pass |
| Documentation updated atomically | ✅ Pass |

#### ⚠️ Warning: Implicit Boolean Tests on Integer Bitfields

In `mlx5_sws_is_any_supported()`:
```c
if (hca_attr->rx_sw_owner_v2 || hca_attr->rx_sw_owner)
    return true;
```

These are `uint8_t` bitfields, not `bool`. Per AGENTS.md guidelines, prefer explicit comparisons:
```c
if (hca_attr->rx_sw_owner_v2 != 0 || hca_attr->rx_sw_owner != 0)
```

Same pattern appears for `tx_sw_owner*` and `esw_sw_owner*` checks.

---

### Summary

| Severity | Issue | Location |
|----------|-------|----------|
| **Warning** | Subject prefix `drivers:` could be more specific | Commit message |
| **Warning** | Implicit boolean tests on integer bitfields | `mlx5.c` |

---

### Recommendation

**Acceptable for merge** — No blocking errors. The warnings are minor style preferences. The patch is well-structured with proper documentation updates and correct tag formatting.


  parent reply	other threads:[~2026-01-13  1:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  9:24 [PATCH 0/4] net/mlx5: future HW devargs defaults and fixes Maayan Kashani
2026-01-12  9:24 ` [PATCH 1/4] drivers: fix flow devarg handling for future HW Maayan Kashani
2026-01-12 18:17   ` Dariusz Sosnowski
2026-01-13  1:20   ` Stephen Hemminger [this message]
2026-01-12  9:24 ` [PATCH 2/4] net/mlx5: fix default memzone requirements in HWS Maayan Kashani
2026-02-11 14:38   ` Bing Zhao
2026-02-12  9:02     ` Dariusz Sosnowski
2026-01-12  9:24 ` [PATCH 3/4] net/mlx5: fix internal HWS pattern template creation Maayan Kashani
2026-01-12 18:18   ` Dariusz Sosnowski
2026-01-12  9:24 ` [PATCH 4/4] net/mlx5: fix redundant control rules in promiscuous mode Maayan Kashani
2026-01-12 18:19   ` Dariusz Sosnowski
2026-01-18 11:40   ` Maayan Kashani
2026-01-14 17:31 ` [PATCH 0/4] net/mlx5: future HW devargs defaults and fixes Stephen Hemminger
2026-02-05 16:06 ` Raslan Darawsheh

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=20260112172030.1ecf0a1a@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=mkashani@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@nvidia.com \
    --cc=viacheslavo@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