From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Lance Richardson <lance.richardson@broadcom.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: limit per-poll Rx representor pkts
Date: Wed, 6 Jan 2021 09:27:32 +0000 [thread overview]
Message-ID: <e6b63511-c01d-1456-021c-a183cadcde60@intel.com> (raw)
In-Reply-To: <20201214185352.252477-1-lance.richardson@broadcom.com>
On 12/14/2020 6:53 PM, Lance Richardson wrote:
> Limit number of representor packets transferred per poll
> to requested burst size.
>
Hi Lance,
Can you please describe the impact of the change? Since it has a fixes line, it
seems it is fixing something but it is not clear what is fixed.
> Fixes: 6dc83230b43b ("net/bnxt: support port representor data path")
> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
> Reviewed-by: Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>
> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
> Cc: stable@dpdk.org
> ---
> drivers/net/bnxt/bnxt_rxr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/bnxt/bnxt_rxr.c b/drivers/net/bnxt/bnxt_rxr.c
> index 2b1dd97617..ffdeeecc3a 100644
> --- a/drivers/net/bnxt/bnxt_rxr.c
> +++ b/drivers/net/bnxt/bnxt_rxr.c
> @@ -901,7 +901,7 @@ uint16_t bnxt_recv_pkts(void *rx_queue, struct rte_mbuf **rx_pkts,
> }
>
> raw_cons = NEXT_RAW_CMP(raw_cons);
> - if (nb_rx_pkts == nb_pkts || evt)
> + if (nb_rx_pkts == nb_pkts || nb_rep_rx_pkts == nb_pkts || evt)
> break;
> /* Post some Rx buf early in case of larger burst processing */
> if (nb_rx_pkts == BNXT_RX_POST_THRESH)
>
next prev parent reply other threads:[~2021-01-06 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 18:53 Lance Richardson
2020-12-17 23:54 ` Ajit Khaparde
2021-01-06 9:27 ` Ferruh Yigit [this message]
2021-01-06 20:54 ` Lance Richardson
2021-01-07 15:33 ` Ferruh Yigit
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=e6b63511-c01d-1456-021c-a183cadcde60@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=lance.richardson@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=venkatkumar.duvvuru@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).