DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
	 Somnath Kotur <somnath.kotur@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: refactor Rx ring cleanup for representors
Date: Tue, 26 Oct 2021 18:52:57 -0700	[thread overview]
Message-ID: <CACZ4nhvBiC1wuSmi01XfPFQTNySwZY7Q7BHU7r6zGfVMZw0Ogg@mail.gmail.com> (raw)
In-Reply-To: <20211026051455.84103-1-ajit.khaparde@broadcom.com>

On Mon, Oct 25, 2021 at 10:14 PM Ajit Khaparde
<ajit.khaparde@broadcom.com> wrote:
>
> Rx ring for representors does not use aggregation rings for Rx.
> Instead they use simple software buffers for handling Rx packets.
> So there is no need to use the same cleanup routine as done by
> the non-representor code path.
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Acked-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> Acked-by: Somnath Kotur <somnath.kotur@broadcom.com>
Patch applied to dpdk-next-net-brcm.

> ---
>  drivers/net/bnxt/bnxt_reps.c | 22 +++++++++++++++++++++-
>  1 file changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/bnxt/bnxt_reps.c b/drivers/net/bnxt/bnxt_reps.c
> index 1c07db3ca9..92beea3558 100644
> --- a/drivers/net/bnxt/bnxt_reps.c
> +++ b/drivers/net/bnxt/bnxt_reps.c
> @@ -386,6 +386,26 @@ static int bnxt_vfr_alloc(struct rte_eth_dev *vfr_ethdev)
>         return rc;
>  }
>
> +static void bnxt_vfr_rx_queue_release_mbufs(struct bnxt_rx_queue *rxq)
> +{
> +       struct rte_mbuf **sw_ring;
> +       unsigned int i;
> +
> +       if (!rxq || !rxq->rx_ring)
> +               return;
> +
> +       sw_ring = rxq->rx_ring->rx_buf_ring;
> +       if (sw_ring) {
> +               for (i = 0; i < rxq->rx_ring->rx_ring_struct->ring_size; i++) {
> +                       if (sw_ring[i]) {
> +                               if (sw_ring[i] != &rxq->fake_mbuf)
> +                                       rte_pktmbuf_free_seg(sw_ring[i]);
> +                               sw_ring[i] = NULL;
> +                       }
> +               }
> +       }
> +}
> +
>  static void bnxt_rep_free_rx_mbufs(struct bnxt_representor *rep_bp)
>  {
>         struct bnxt_rx_queue *rxq;
> @@ -393,7 +413,7 @@ static void bnxt_rep_free_rx_mbufs(struct bnxt_representor *rep_bp)
>
>         for (i = 0; i < rep_bp->rx_nr_rings; i++) {
>                 rxq = rep_bp->rx_queues[i];
> -               bnxt_rx_queue_release_mbufs(rxq);
> +               bnxt_vfr_rx_queue_release_mbufs(rxq);
>         }
>  }
>
> --
> 2.30.1 (Apple Git-130)
>

      reply	other threads:[~2021-10-27  1:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  5:14 Ajit Khaparde
2021-10-27  1:52 ` 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=CACZ4nhvBiC1wuSmi01XfPFQTNySwZY7Q7BHU7r6zGfVMZw0Ogg@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=somnath.kotur@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).