From: Somnath Kotur <somnath.kotur@broadcom.com>
To: dev <dev@dpdk.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix max ring count calculation
Date: Wed, 10 Jun 2020 17:26:49 +0530 [thread overview]
Message-ID: <CAOBf=mtcuDBsXTkE5VVq_yvUtaXp3kH0=K0oh=+jWwqFP9642A@mail.gmail.com> (raw)
In-Reply-To: <20200610114344.22097-1-somnath.kotur@broadcom.com>
On Wed, Jun 10, 2020 at 5:18 PM Somnath Kotur
<somnath.kotur@broadcom.com> wrote:
>
> Max Rx Ring count could be < Max stat contexts. While accounting
> for stat contexts, this should be also considered and
> the max ring count adjusted accordingly.
>
> Fixes: f03e66cb64ce ("net/bnxt: limit queue count for NS3/Stingray devices")
> Cc: stable@dpdk.org
>
> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com>
> ---
> drivers/net/bnxt/bnxt.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/bnxt/bnxt.h b/drivers/net/bnxt/bnxt.h
> index 586d3f5..12fed1e 100644
> --- a/drivers/net/bnxt/bnxt.h
> +++ b/drivers/net/bnxt/bnxt.h
> @@ -653,10 +653,10 @@ struct bnxt {
> #define MAX_STINGRAY_RINGS 128U
> /* For sake of symmetry, max Tx rings == max Rx rings, one stat ctx for each */
> #define BNXT_MAX_RX_RINGS(bp) \
> - (BNXT_STINGRAY(bp) ? RTE_MIN(RTE_MIN(bp->max_rx_rings, \
> + (BNXT_STINGRAY(bp) ? RTE_MIN(RTE_MIN(bp->max_rx_rings / 2U, \
> MAX_STINGRAY_RINGS), \
> bp->max_stat_ctx / 2U) : \
> - RTE_MIN(bp->max_rx_rings, \
> + RTE_MIN(bp->max_rx_rings / 2U, \
> bp->max_stat_ctx / 2U))
> #define BNXT_MAX_TX_RINGS(bp) \
> (RTE_MIN((bp)->max_tx_rings, BNXT_MAX_RX_RINGS(bp)))
> --
> 1.8.3.1
>
Sorry, kindly ignore this patch, got sent out by accident (prev history)
next prev parent reply other threads:[~2020-06-10 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 11:43 Somnath Kotur
2020-06-10 11:56 ` Somnath Kotur [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-24 11:00 Somnath Kotur
2020-04-24 17:58 ` Ajit Khaparde
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='CAOBf=mtcuDBsXTkE5VVq_yvUtaXp3kH0=K0oh=+jWwqFP9642A@mail.gmail.com' \
--to=somnath.kotur@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).