patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: Somnath Kotur <somnath.kotur@broadcom.com>,
	dpdk-dev <dev@dpdk.org>,  dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 1/1] net/bnxt: fix Rx buffer posting
Date: Thu, 18 Mar 2021 20:50:59 -0700	[thread overview]
Message-ID: <CACZ4nhspwGi5sNKG-mYj5Q+K1FQE+_C9R9eS900fD0MxL+h+4g@mail.gmail.com> (raw)
In-Reply-To: <20210318195213.683281-1-lance.richardson@broadcom.com>

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

On Thu, Mar 18, 2021 at 12:52 PM Lance Richardson
<lance.richardson@broadcom.com> wrote:
>
> Remove early buffer posting logic from burst receive loop to address
> several issues:
>    - Posting receive descriptors without first posting completion
>      entries risks overflowing the completion queue.
>    - Posting receive descriptors without updating rx_raw_prod
>      creates the possibility that the receive descriptor doorbell
>      can be written twice with the same value.
>    - Having this logic in the inner descriptor processing loop
>      can impact performance.
>
> Fixes: 637e34befd9c ("net/bnxt: optimize Rx processing")
> Fixes: 04067844a3e9 ("net/bnxt: reduce CQ queue size without aggregation ring")
> Cc: stable@dpdk.org
>
> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
> Reviewed-by: Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>
Patch applied to dpdk-next-net-brcm.

> ---
>  drivers/net/bnxt/bnxt_rxr.c | 3 ---
>  drivers/net/bnxt/bnxt_rxr.h | 2 --
>  2 files changed, 5 deletions(-)
>
> diff --git a/drivers/net/bnxt/bnxt_rxr.c b/drivers/net/bnxt/bnxt_rxr.c
> index c72545ada7..7179c6cb30 100644
> --- a/drivers/net/bnxt/bnxt_rxr.c
> +++ b/drivers/net/bnxt/bnxt_rxr.c
> @@ -1018,9 +1018,6 @@ 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 || 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)
> -                       bnxt_db_write(&rxr->rx_db, rxr->rx_raw_prod);
>         }
>
>         cpr->cp_raw_cons = raw_cons;
> diff --git a/drivers/net/bnxt/bnxt_rxr.h b/drivers/net/bnxt/bnxt_rxr.h
> index a6fdd7767a..b43256e03e 100644
> --- a/drivers/net/bnxt/bnxt_rxr.h
> +++ b/drivers/net/bnxt/bnxt_rxr.h
> @@ -41,8 +41,6 @@ static inline uint16_t bnxt_tpa_start_agg_id(struct bnxt *bp,
>         (((cmp)->agg_bufs_v1 & RX_PKT_CMPL_AGG_BUFS_MASK) >> \
>                 RX_PKT_CMPL_AGG_BUFS_SFT)
>
> -#define BNXT_RX_POST_THRESH    32
> -
>  /* Number of descriptors to process per inner loop in vector mode. */
>  #define RTE_BNXT_DESCS_PER_LOOP                4U
>
> --
> 2.25.1
>

      reply	other threads:[~2021-03-19  3:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 19:52 Lance Richardson
2021-03-19  3:50 ` 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=CACZ4nhspwGi5sNKG-mYj5Q+K1FQE+_C9R9eS900fD0MxL+h+4g@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=lance.richardson@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).