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>
Subject: Re: [PATCH v2] net/bnxt: fix ring calculation for representors
Date: Wed, 9 Feb 2022 10:19:23 -0800	[thread overview]
Message-ID: <CACZ4nhuJ-xDc_zJeydEHj6RrNVob1XF=a9MS1f=XG11P2z0D4A@mail.gmail.com> (raw)
In-Reply-To: <20220209174219.35650-1-ajit.khaparde@broadcom.com>

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

On Wed, Feb 9, 2022 at 9:42 AM Ajit Khaparde <ajit.khaparde@broadcom.com> wrote:
>
> Currently the Tx and Rx ring count for representors is fixed.
> It does not consider the number of rings created for the parent
> function. And that can cause issues not only during initialization
> but while running traffic.
> Instead check the number of rings created for the parent function
> while configuring the ring resources for representors.
> In some cases VF rep ring init may happen before the parent function's
> rings have been setup. And this can cause representor ring count to be
> configured as 0. In such cases, initialize the VF representor
> ring count to 8.
>
> Fixes: 322bd6e70272 ("net/bnxt: add port representor infrastructure")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
> Reviewed-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
v1->v2: sets a default queue count if under some cases we find to be 0.

Patch applied to dpdk-next-net-brcm.

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

      reply	other threads:[~2022-02-09 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09  5:58 [PATCH] " Ajit Khaparde
2022-02-09 15:37 ` Ajit Khaparde
2022-02-09 17:34   ` Ajit Khaparde
2022-02-09 17:42     ` [PATCH v2] " Ajit Khaparde
2022-02-09 18:19       ` 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='CACZ4nhuJ-xDc_zJeydEHj6RrNVob1XF=a9MS1f=XG11P2z0D4A@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --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).