From: ALOK TIWARI <alok.a.tiwari@oracle.com>
To: Bhargava Marreddy <bhargava.marreddy@broadcom.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
vsrama-krishna.nemani@broadcom.com, vikas.gupta@broadcom.com,
Rajashekar Hudumula <rajashekar.hudumula@broadcom.com>
Subject: Re: [v7, net-next 09/10] bng_en: Register default VNIC
Date: Thu, 18 Sep 2025 01:48:29 +0530 [thread overview]
Message-ID: <aa898848-810e-4a6f-9fcf-0289e620229d@oracle.com> (raw)
In-Reply-To: <20250911193505.24068-10-bhargava.marreddy@broadcom.com>
On 9/12/2025 1:05 AM, Bhargava Marreddy wrote:
> +int bnge_hwrm_vnic_cfg(struct bnge_net *bn, struct bnge_vnic_info *vnic)
> +{
> + struct bnge_rx_ring_info *rxr = &bn->rx_ring[0];
> + struct hwrm_vnic_cfg_input *req;
> + struct bnge_dev *bd = bn->bd;
> + int rc;
> +
> + rc = bnge_hwrm_req_init(bd, req, HWRM_VNIC_CFG);
> + if (rc)
> + return rc;
> +
> + req->default_rx_ring_id =
> + cpu_to_le16(rxr->rx_ring_struct.fw_ring_id);
> + req->default_cmpl_ring_id =
> + cpu_to_le16(bnge_cp_ring_for_rx(rxr));
> + req->enables =
> + cpu_to_le32(VNIC_CFG_REQ_ENABLES_DEFAULT_RX_RING_ID |
> + VNIC_CFG_REQ_ENABLES_DEFAULT_CMPL_RING_ID);
> + vnic->mru = bd->netdev->mtu + ETH_HLEN + VLAN_HLEN;
nit: does "struct bnge_dev" hold a netdev ?
if not should be bn->netdev->mtu.
> + req->mru = cpu_to_le16(vnic->mru);
> +
> + req->vnic_id = cpu_to_le16(vnic->fw_vnic_id);
> +
> + if (bd->flags & BNGE_EN_STRIP_VLAN)
> + req->flags |= cpu_to_le32(VNIC_CFG_REQ_FLAGS_VLAN_STRIP_MODE);
> + if (vnic->vnic_id == BNGE_VNIC_DEFAULT && bnge_aux_registered(bd))
> + req->flags |= cpu_to_le32(BNGE_VNIC_CFG_ROCE_DUAL_MODE);
> +
> + return bnge_hwrm_req_send(bd, req);
> +}
Thanks,
Alok
next prev parent reply other threads:[~2025-09-17 20:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 19:34 [v7, net-next 00/10] Add more functionality to BNGE Bhargava Marreddy
2025-09-11 19:34 ` [v7, net-next 01/10] bng_en: make bnge_alloc_ring() self-unwind on failure Bhargava Marreddy
2025-09-16 15:12 ` Simon Horman
2025-09-18 9:50 ` Bhargava Chenna Marreddy
2025-09-18 19:06 ` Simon Horman
2025-09-11 19:34 ` [v7, net-next 02/10] bng_en: Add initial support for RX and TX rings Bhargava Marreddy
2025-09-11 19:34 ` [v7, net-next 03/10] bng_en: Add initial support for CP and NQ rings Bhargava Marreddy
2025-09-16 14:54 ` Simon Horman
2025-09-18 9:40 ` Bhargava Chenna Marreddy
2025-09-11 19:34 ` [v7, net-next 04/10] bng_en: Introduce VNIC Bhargava Marreddy
2025-09-11 19:35 ` [v7, net-next 05/10] bng_en: Initialise core resources Bhargava Marreddy
2025-09-16 15:45 ` Simon Horman
2025-09-18 10:49 ` Bhargava Chenna Marreddy
2025-09-11 19:35 ` [v7, net-next 06/10] bng_en: Allocate packet buffers Bhargava Marreddy
2025-09-14 20:31 ` Jakub Kicinski
2025-09-15 17:56 ` Bhargava Chenna Marreddy
2025-09-15 21:52 ` Jakub Kicinski
2025-09-11 19:35 ` [v7, net-next 07/10] bng_en: Allocate stat contexts Bhargava Marreddy
2025-09-11 19:35 ` [v7, net-next 08/10] bng_en: Register rings with the firmware Bhargava Marreddy
2025-09-16 15:51 ` Simon Horman
2025-09-18 10:41 ` Bhargava Chenna Marreddy
2025-09-18 19:06 ` Simon Horman
2025-09-17 20:14 ` [External] : " ALOK TIWARI
2025-09-11 19:35 ` [v7, net-next 09/10] bng_en: Register default VNIC Bhargava Marreddy
2025-09-17 20:18 ` ALOK TIWARI [this message]
2025-09-19 6:28 ` Bhargava Chenna Marreddy
2025-09-11 19:35 ` [v7, net-next 10/10] bng_en: Configure " Bhargava Marreddy
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=aa898848-810e-4a6f-9fcf-0289e620229d@oracle.com \
--to=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=bhargava.marreddy@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=rajashekar.hudumula@broadcom.com \
--cc=vikas.gupta@broadcom.com \
--cc=vsrama-krishna.nemani@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
all inboxes | Powered by JetHome®