From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew+netdev@lunn.ch,
pavan.chebbi@broadcom.com, andrew.gospodarek@broadcom.com,
somnath.kotur@broadcom.com,
Hongguang Gao <hongguang.gao@broadcom.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [PATCH net-next 06/10] bnxt_en: Refactor RX/RX AGG ring parameters setup for P5_PLUS
Date: Mon, 13 Jan 2025 09:27:31 +0100 [thread overview]
Message-ID: <Z4TOc/M4eUqQPLR2@mev-dev.igk.intel.com> (raw)
In-Reply-To: <20250113063927.4017173-7-michael.chan@broadcom.com>
On Sun, Jan 12, 2025 at 10:39:23PM -0800, Michael Chan wrote:
> There is some common code for setting up RX and RX AGG ring allocation
> parameters for P5_PLUS chips. Refactor the logic into a new function.
>
> Reviewed-by: Hongguang Gao <hongguang.gao@broadcom.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Signed-off-by: Michael Chan <michael.chan@broadcom.com>
> ---
> drivers/net/ethernet/broadcom/bnxt/bnxt.c | 58 +++++++++++------------
> 1 file changed, 28 insertions(+), 30 deletions(-)
>
> diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> index 4336a5b54289..c862250d3b77 100644
> --- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> @@ -6917,6 +6917,28 @@ static void bnxt_hwrm_ring_grp_free(struct bnxt *bp)
> hwrm_req_drop(bp, req);
> }
>
> +static void bnxt_set_rx_ring_params_p5(struct bnxt *bp, u32 ring_type,
> + struct hwrm_ring_alloc_input *req,
> + struct bnxt_ring_struct *ring)
> +{
> + struct bnxt_ring_grp_info *grp_info = &bp->grp_info[ring->grp_idx];
> + u32 enables = RING_ALLOC_REQ_ENABLES_RX_BUF_SIZE_VALID;
> +
> + if (ring_type == HWRM_RING_ALLOC_AGG) {
> + req->ring_type = RING_ALLOC_REQ_RING_TYPE_RX_AGG;
> + req->rx_ring_id = cpu_to_le16(grp_info->rx_fw_ring_id);
> + req->rx_buf_size = cpu_to_le16(BNXT_RX_PAGE_SIZE);
> + enables |= RING_ALLOC_REQ_ENABLES_RX_RING_ID_VALID;
> + } else {
> + req->rx_buf_size = cpu_to_le16(bp->rx_buf_use_size);
> + if (NET_IP_ALIGN == 2)
> + req->flags =
> + cpu_to_le16(RING_ALLOC_REQ_FLAGS_RX_SOP_PAD);
> + }
> + req->stat_ctx_id = cpu_to_le32(grp_info->fw_stats_ctx);
> + req->enables |= cpu_to_le32(enables);
> +}
> +
> static int hwrm_ring_alloc_send_msg(struct bnxt *bp,
> struct bnxt_ring_struct *ring,
> u32 ring_type, u32 map_index)
> @@ -6968,37 +6990,13 @@ static int hwrm_ring_alloc_send_msg(struct bnxt *bp,
> break;
> }
> case HWRM_RING_ALLOC_RX:
> - req->ring_type = RING_ALLOC_REQ_RING_TYPE_RX;
> - req->length = cpu_to_le32(bp->rx_ring_mask + 1);
> - if (bp->flags & BNXT_FLAG_CHIP_P5_PLUS) {
> - u16 flags = 0;
> -
> - /* Association of rx ring with stats context */
> - grp_info = &bp->grp_info[ring->grp_idx];
> - req->rx_buf_size = cpu_to_le16(bp->rx_buf_use_size);
> - req->stat_ctx_id = cpu_to_le32(grp_info->fw_stats_ctx);
> - req->enables |= cpu_to_le32(
> - RING_ALLOC_REQ_ENABLES_RX_BUF_SIZE_VALID);
> - if (NET_IP_ALIGN == 2)
> - flags = RING_ALLOC_REQ_FLAGS_RX_SOP_PAD;
> - req->flags = cpu_to_le16(flags);
> - }
> - break;
> case HWRM_RING_ALLOC_AGG:
> - if (bp->flags & BNXT_FLAG_CHIP_P5_PLUS) {
> - req->ring_type = RING_ALLOC_REQ_RING_TYPE_RX_AGG;
> - /* Association of agg ring with rx ring */
> - grp_info = &bp->grp_info[ring->grp_idx];
> - req->rx_ring_id = cpu_to_le16(grp_info->rx_fw_ring_id);
> - req->rx_buf_size = cpu_to_le16(BNXT_RX_PAGE_SIZE);
> - req->stat_ctx_id = cpu_to_le32(grp_info->fw_stats_ctx);
> - req->enables |= cpu_to_le32(
> - RING_ALLOC_REQ_ENABLES_RX_RING_ID_VALID |
> - RING_ALLOC_REQ_ENABLES_RX_BUF_SIZE_VALID);
> - } else {
> - req->ring_type = RING_ALLOC_REQ_RING_TYPE_RX;
> - }
> - req->length = cpu_to_le32(bp->rx_agg_ring_mask + 1);
> + req->ring_type = RING_ALLOC_REQ_RING_TYPE_RX;
> + req->length = (ring_type == HWRM_RING_ALLOC_RX) ?
> + cpu_to_le32(bp->rx_ring_mask + 1) :
> + cpu_to_le32(bp->rx_agg_ring_mask + 1);
> + if (bp->flags & BNXT_FLAG_CHIP_P5_PLUS)
> + bnxt_set_rx_ring_params_p5(bp, ring_type, req, ring);
> break;
> case HWRM_RING_ALLOC_CMPL:
> req->ring_type = RING_ALLOC_REQ_RING_TYPE_L2_CMPL;
> --
> 2.30.1
Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
next prev parent reply other threads:[~2025-01-13 8:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 6:39 [PATCH net-next 00/10] bnxt_en: Add NPAR 1.2 and TPH support Michael Chan
2025-01-13 6:39 ` [PATCH net-next 01/10] bnxt_en: Set NAPR 1.2 support when registering with firmware Michael Chan
2025-01-13 7:56 ` Michal Swiatkowski
2025-01-13 6:39 ` [PATCH net-next 02/10] bnxt_en Refactor completion ring allocation logic for P5_PLUS chips Michael Chan
2025-01-13 7:59 ` Michal Swiatkowski
2025-01-13 6:39 ` [PATCH net-next 03/10] bnxt_en: Refactor TX ring allocation logic Michael Chan
2025-01-13 8:02 ` Michal Swiatkowski
2025-01-13 6:39 ` [PATCH net-next 04/10] bnxt_en: Refactor completion ring free routine Michael Chan
2025-01-13 8:06 ` Michal Swiatkowski
2025-01-13 6:39 ` [PATCH net-next 05/10] bnxt_en: Refactor bnxt_free_tx_rings() to free per Tx ring Michael Chan
2025-01-13 8:17 ` Michal Swiatkowski
2025-01-13 6:39 ` [PATCH net-next 06/10] bnxt_en: Refactor RX/RX AGG ring parameters setup for P5_PLUS Michael Chan
2025-01-13 8:27 ` Michal Swiatkowski [this message]
2025-01-13 6:39 ` [PATCH net-next 07/10] bnxt_en: Pass NQ ID to the FW when allocating RX/RX AGG rings Michael Chan
2025-01-13 8:29 ` Michal Swiatkowski
2025-01-13 6:39 ` [PATCH net-next 08/10] bnxt_en: Reallocate Rx completion ring for TPH support Michael Chan
2025-01-13 8:35 ` Michal Swiatkowski
2025-01-14 21:42 ` Michael Chan
2025-01-15 5:58 ` Michal Swiatkowski
2025-01-13 6:39 ` [PATCH net-next 09/10] bnxt_en: Extend queue stop/start for Tx rings Michael Chan
2025-01-13 8:40 ` Michal Swiatkowski
2025-01-14 2:05 ` Somnath Kotur
2025-01-15 1:29 ` Michael Chan
2025-01-13 16:01 ` Bjorn Helgaas
2025-01-14 4:57 ` Somnath Kotur
2025-01-14 8:48 ` kernel test robot
2025-01-14 11:23 ` kernel test robot
2025-01-13 6:39 ` [PATCH net-next 10/10] bnxt_en: Add TPH support in BNXT driver Michael Chan
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=Z4TOc/M4eUqQPLR2@mev-dev.igk.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hongguang.gao@broadcom.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=somnath.kotur@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;
as well as URLs for NNTP newsgroup(s).