From: netdev-bot+sashiko@kernel.org
To: siva.kallam@broadcom.com
Cc: leonro@nvidia.com, jgg@nvidia.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org,
vikas.gupta@broadcom.com, ajit.khaparde@broadcom.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, sachin.holla@broadcom.com,
dharmender.garg@broadcom.com
Subject: Re: [net-next v2 1/3] bnge: Add infrastructure support for RoCE MPC channels
Date: Sat, 10 Oct 2026 16:45:22 +0000 [thread overview]
Message-ID: <179165072240.434549.10870506597507225182@kernel.org> (raw)
In-Reply-To: <20261006161256.1493672-2-siva.kallam@broadcom.com>
Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.
Low priority / nit picks for your consideration:
- [Low] The patch has no consumer, and its subject and body promise more
than it does.
--
bnge: Add infrastructure support for RoCE MPC channels
This patch adds a bar1 pointer to struct bnge_auxr_dev. It also fills that
pointer in from bd->bar1 in bnge_set_auxr_dev_info(), next to the existing
bar0. The commit message says follow-on patches will use it to send RoCE
commands to the firmware over the MPC channels.
> diff --git a/drivers/net/ethernet/broadcom/bnge/bnge_auxr.c b/drivers/net/ethernet/broadcom/bnge/bnge_auxr.c
> index 0955b488b6fea..87ae40eab5926 100644
> --- a/drivers/net/ethernet/broadcom/bnge/bnge_auxr.c
> +++ b/drivers/net/ethernet/broadcom/bnge/bnge_auxr.c
> @@ -181,6 +181,7 @@ static void bnge_set_auxr_dev_info(struct bnge_auxr_dev *auxr_dev,
> auxr_dev->pf_port_id = bd->pf.port_id;
> auxr_dev->en_state = bd->state;
> auxr_dev->bar0 = bd->bar0;
> + auxr_dev->bar1 = bd->bar1;
> }
>
> void bnge_rdma_aux_device_add(struct bnge_dev *bd)
> diff --git a/drivers/net/ethernet/broadcom/bnge/bnge_auxr.h b/drivers/net/ethernet/broadcom/bnge/bnge_auxr.h
> index 6c5c15ef2b0a7..13cb9289f5b89 100644
> --- a/drivers/net/ethernet/broadcom/bnge/bnge_auxr.h
> +++ b/drivers/net/ethernet/broadcom/bnge/bnge_auxr.h
> @@ -46,6 +46,7 @@ struct bnge_auxr_dev {
> struct net_device *net;
> struct pci_dev *pdev;
> void __iomem *bar0;
> + void __iomem *bar1;
[Severity: Low]
Does anything read auxr_dev->bar1? This commit has no user of the new
field. The later patches in the series ("bnge: Update HSI" and "bnge:
reserve TX/completion rings for the RoCE MPC channel") don't add one either.
drivers/infiniband/hw/bng_re/ dereferences neither ->bar0 nor ->bar1. It
still maps its own regions, in bng_re_map_cmdq_mbox():
mbox->reg.bar_base = pci_resource_start(pdev, mbox->reg.bar_id);
and in bng_re_map_creq_db():
creq_db->reg.bar_base = pci_resource_start(pdev, creq_db->reg.bar_id);
Could this assignment and the new field move into the bng_re patch that
first uses auxr_dev->bar1?
The subject and body also describe more than the patch does:
bnge: Add infrastructure support for RoCE MPC channels
Add the initial L2 driver plumbing for RoCE MPC (PRIMATE channel)
support:
Nothing in the change is specific to MPC or PRIMATE. The body also has a
bullet list with only one item.
If the field stays in this patch, could the message say that it only
passes the existing L2 BAR1 doorbell mapping to the RoCE auxiliary device?
>
> struct bnge_msix_info msix_info[BNGE_MAX_ROCE_MSIX];
>
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261006161256.1493672-1-siva.kallam%40broadcom.com
next prev parent reply other threads:[~2026-10-10 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 16:12 [net-next v2 0/3] bnge changes for RoCE driver Siva Reddy Kallam
2026-10-06 16:12 ` [net-next v2 1/3] bnge: Add infrastructure support for RoCE MPC channels Siva Reddy Kallam
2026-10-10 16:45 ` netdev-bot+sashiko [this message]
2026-10-06 16:12 ` [net-next v2 2/3] bnge: Update HSI Siva Reddy Kallam
2026-10-06 16:12 ` [net-next v2 3/3] bnge: reserve TX/completion rings for the RoCE MPC channel Siva Reddy Kallam
2026-10-10 16:45 ` netdev-bot+sashiko
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=179165072240.434549.10870506597507225182@kernel.org \
--to=netdev-bot+sashiko@kernel.org \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dharmender.garg@broadcom.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sachin.holla@broadcom.com \
--cc=siva.kallam@broadcom.com \
--cc=vikas.gupta@broadcom.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