All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajitkhaparde@gmail.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	 Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>,
	dev@dpdk.org, ferruh.yigit@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: limit per-poll Rx representor pkts
Date: Thu, 17 Dec 2020 15:54:48 -0800	[thread overview]
Message-ID: <CAD6mc5aY5bEDpzvr=FgNqvmztQFACtmdwTnRQynd0MkOW_bGBQ@mail.gmail.com> (raw)
In-Reply-To: <20201214185352.252477-1-lance.richardson@broadcom.com>

On Mon, Dec 14, 2020 at 10:54 AM Lance Richardson
<lance.richardson@broadcom.com> wrote:
>
> Limit number of representor packets transferred per poll
> to requested burst size.
>
> 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

Patch applied to dpdk-next-net-brcm. Thanks

> ---
>  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)
> --
> 2.25.1
>
>
> --
> This electronic communication and the information and any files transmitted
> with it, or attached to it, are confidential and are intended solely for
> the use of the individual or entity to whom it is addressed and may contain
> information that is confidential, legally privileged, protected by privacy
> laws, or otherwise restricted from disclosure to anyone else. If you are
> not the intended recipient or the person responsible for delivering the
> e-mail to the intended recipient, you are hereby notified that any use,
> copying, distributing, dissemination, forwarding, printing, or copying of
> this e-mail is strictly prohibited. If you received this e-mail in error,
> please return the e-mail to the sender, delete it from your computer, and
> destroy any printed copy of it.



-- 
Ajit Khaparde

  reply	other threads:[~2020-12-17 23:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 18:53 [dpdk-dev] [PATCH] net/bnxt: limit per-poll Rx representor pkts Lance Richardson
2020-12-17 23:54 ` Ajit Khaparde [this message]
2021-01-06  9:27 ` Ferruh Yigit
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='CAD6mc5aY5bEDpzvr=FgNqvmztQFACtmdwTnRQynd0MkOW_bGBQ@mail.gmail.com' \
    --to=ajitkhaparde@gmail.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.