From: Simon Horman <horms@kernel.org>
To: Tariq Toukan <tariqt@nvidia.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Carolina Jubran <cjubran@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
open list <linux-kernel@vger.kernel.org>,
Shahar Shitrit <shshitrit@nvidia.com>,
Leon Romanovsky <leon@kernel.org>, Mark Bloch <mbloch@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>
Subject: Re: [PATCH net-next 1/5] net/mlx5: nodnic: Introduce the mlx5_nodnic driver
Date: Fri, 2 Oct 2026 18:16:04 +0100 [thread overview]
Message-ID: <20261002171604.GM13925@horms.kernel.org> (raw)
In-Reply-To: <20260930125708.144767-2-tariqt@nvidia.com>
On Wed, Sep 30, 2026 at 03:57:04PM +0300, Tariq Toukan wrote:
> From: Shahar Shitrit <shshitrit@nvidia.com>
>
> Introduce mlx5_nodnic, a driver for DRAM-less NVIDIA Mellanox NIC
> functions.
>
> It defines a lightweight NIC function intended for contexts where local
> DRAM is unavailable or too costly: embedded controllers, management
> planes, pre-boot environments, or any resource-constrained instantiation
> of a ConnectX NIC. The hardware sends and receives ordinary Ethernet
> frames via SQs, RQs and CQs. There is no encapsulation, no private
> protocol, and no FW interposition: packets are forwarded as standard
> Ethernet between whatever peers are connected to the function. The
> interface is documented in the HW spec and has been in production in
> non-Linux OS drivers for over a decade.
>
> This patch implements the PCI probe and remove flows, including FLR,
> firmware readiness, interface negotiation and capability discovery,
> followed by port and ring configuration.
>
> It also adds the VSC access layer for PCI configuration-space accesses
> to the initialization segment and to the NODNIC configuration registers.
> Set up the event IRQ for link-state notifications, retrieve the port MAC
> address, and implement the netdev lifecycle, including ndo_open and
> ndo_stop.
>
> Signed-off-by: Shahar Shitrit <shshitrit@nvidia.com>
> Reviewed-by: Carolina Jubran <cjubran@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Unfortunately this patch introduces a number of Sparse warnings.
Which other than looking like they should be addressed
also appears to have gated sashiko-nipa from running.
.../nodnic/nodnic_pci_vsc.c:336:16: warning: cast to restricted __le32
.../nodnic/nodnic_pci_vsc.c:336:16: warning: incorrect type in return expression (different base types)
.../nodnic/nodnic_pci_vsc.c:336:16: expected unsigned int
.../nodnic/nodnic_pci_vsc.c:336:16: got restricted __be32 [usertype]
.../nodnic/nodnic_pci_vsc.c:341:16: warning: cast to restricted __be32
.../nodnic/nodnic_pci_vsc.c:341:16: warning: incorrect type in return expression (different base types)
.../nodnic/nodnic_pci_vsc.c:341:16: expected unsigned int
.../nodnic/nodnic_pci_vsc.c:341:16: got restricted __le32 [usertype]
.../nodnic/nodnic_pci_vsc.c:363:25: warning: cast to restricted __le32
.../nodnic/nodnic_pci_vsc.c:407:17: warning: cast to restricted __le32
.../nodnic/nodnic_pci_vsc.c:415:14: warning: incorrect type in assignment (different base types)
.../nodnic/nodnic_pci_vsc.c:415:14: expected unsigned int [usertype] data
.../nodnic/nodnic_pci_vsc.c:415:14: got restricted __le32 [usertype]
.../nodnic/en_cfg.c:28:16: warning: incorrect type in assignment (different base types)
.../nodnic/en_cfg.c:28:16: expected unsigned int [usertype] addr_h
.../nodnic/en_cfg.c:28:16: got restricted __be32 [usertype]
.../nodnic/en_cfg.c:117:15: warning: incorrect type in assignment (different base types)
.../nodnic/en_cfg.c:117:15: expected unsigned int [usertype] dbr_h
.../nodnic/en_cfg.c:117:15: got restricted __be32 [usertype]
.../nodnic/en_cfg.c:237:15: warning: incorrect type in assignment (different base types)
.../nodnic/en_cfg.c:237:15: expected unsigned int [usertype] dbr_l
.../nodnic/en_cfg.c:237:15: got restricted __be32 [usertype]
.../nodnic/en_cfg.c:248:15: warning: incorrect type in assignment (different base types)
.../nodnic/en_cfg.c:248:15: expected unsigned int [usertype] dbr_h
.../nodnic/en_cfg.c:248:15: got restricted __be32 [usertype]
--
pw-bot: changes-requested
next prev parent reply other threads:[~2026-10-02 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 12:57 [PATCH net-next 0/5] net/mlx5: Introduce mlx5_nodnic, a driver for DRAM-less NVIDIA Mellanox NIC functions Tariq Toukan
2026-09-30 12:57 ` [PATCH net-next 1/5] net/mlx5: nodnic: Introduce the mlx5_nodnic driver Tariq Toukan
2026-10-02 17:16 ` Simon Horman [this message]
2026-09-30 12:57 ` [PATCH net-next 2/5] net/mlx5: nodnic: Implement data path Tariq Toukan
2026-09-30 12:57 ` [PATCH net-next 3/5] net/mlx5: nodnic: Add TX/RX statistics Tariq Toukan
2026-09-30 12:57 ` [PATCH net-next 4/5] net/mlx5: nodnic: Add ethtool driver info Tariq Toukan
2026-09-30 12:57 ` [PATCH net-next 5/5] net/mlx5: nodnic: Add health monitoring Tariq Toukan
2026-10-02 17:17 ` [PATCH net-next 0/5] net/mlx5: Introduce mlx5_nodnic, a driver for DRAM-less NVIDIA Mellanox NIC functions Simon Horman
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=20261002171604.GM13925@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=shshitrit@nvidia.com \
--cc=tariqt@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
all inboxes | Powered by JetHome®