patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dpdk-dev <dev@dpdk.org>
Cc: dpdk stable <stable@dpdk.org>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	 Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [PATCH] net/bnxt: set HW coalescing parameters
Date: Wed, 9 Feb 2022 07:37:20 -0800	[thread overview]
Message-ID: <CACZ4nhv-34BrU=GZiQTJeD5CHhAuwCb88NLtKu7dLx35rM2EqQ@mail.gmail.com> (raw)
In-Reply-To: <20220209055746.88699-1-ajit.khaparde@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]

On Tue, Feb 8, 2022 at 9:57 PM Ajit Khaparde <ajit.khaparde@broadcom.com> wrote:
>
> Set coalescing parameters correctly for Rx completion rings.
> This is not being done for the Rx completion rings currently.
>
> Fixes: 657c2a7f1dd4 ("net/bnxt: create aggregation rings when needed")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com>
> Reviewed-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Patch applied to dpdk-next-net-brcm.

> ---
>  drivers/net/bnxt/bnxt_ring.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/net/bnxt/bnxt_ring.c b/drivers/net/bnxt/bnxt_ring.c
> index 5c6c27fed7..4cdbb177d9 100644
> --- a/drivers/net/bnxt/bnxt_ring.c
> +++ b/drivers/net/bnxt/bnxt_ring.c
> @@ -752,6 +752,8 @@ int bnxt_alloc_hwrm_rings(struct bnxt *bp)
>                 rc = bnxt_alloc_hwrm_rx_ring(bp, i);
>                 if (rc)
>                         goto err_out;
> +               bnxt_hwrm_set_ring_coal(bp, &coal,
> +                                       rxq->cp_ring->cp_ring_struct->fw_ring_id);
>         }
>
>         /* If something is wrong with Rx ring alloc, skip Tx ring alloc */
> --
> 2.32.0 (Apple Git-132)
>

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]

      reply	other threads:[~2022-02-09 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09  5:57 Ajit Khaparde
2022-02-09 15:37 ` Ajit Khaparde [this message]

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='CACZ4nhv-34BrU=GZiQTJeD5CHhAuwCb88NLtKu7dLx35rM2EqQ@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    /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).