DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix RSS behavior on Thor
Date: Tue, 26 Oct 2021 18:47:58 -0700	[thread overview]
Message-ID: <CACZ4nhubUTbP2aEnWTYTSd12ChDy0kUGekn002sKkb57jQq=8w@mail.gmail.com> (raw)
In-Reply-To: <20211026051430.1389-1-kalesh-anakkur.purayil@broadcom.com>

On Mon, Oct 25, 2021 at 9:54 PM Kalesh A P
<kalesh-anakkur.purayil@broadcom.com> wrote:
>
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> Move the Rx queue state update before bnxt_setup_one_vnic()
> is called. For Thor, rxq->rx_started and eth_dev->data->rx_queue_state[]
> needs to be set for all queues before bnxt_hwrm_vnic_cfg() or
> bnxt_vnic_rss_configure() are called.
>
> Fixes: 0105ea1296c9 ("net/bnxt: support runtime queue setup")
> Cc: stable@dpdk.org
>
> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Acked-by: Somnath Kotur <somnath.kotur@broadcom.com>

Patch applied to dpdk-next-net-brcm.

> ---
>  drivers/net/bnxt/bnxt_ethdev.c | 20 ++++++++++----------
>  1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/net/bnxt/bnxt_ethdev.c b/drivers/net/bnxt/bnxt_ethdev.c
> index 5a34bb9..668e3aa 100644
> --- a/drivers/net/bnxt/bnxt_ethdev.c
> +++ b/drivers/net/bnxt/bnxt_ethdev.c
> @@ -790,6 +790,16 @@ static int bnxt_start_nic(struct bnxt *bp)
>                 goto err_out;
>         }
>
> +       for (j = 0; j < bp->rx_nr_rings; j++) {
> +               struct bnxt_rx_queue *rxq = bp->rx_queues[j];
> +
> +               if (!rxq->rx_deferred_start) {
> +                       bp->eth_dev->data->rx_queue_state[j] =
> +                               RTE_ETH_QUEUE_STATE_STARTED;
> +                       rxq->rx_started = true;
> +               }
> +       }
> +
>         /* default vnic 0 */
>         rc = bnxt_setup_one_vnic(bp, 0);
>         if (rc)
> @@ -813,16 +823,6 @@ static int bnxt_start_nic(struct bnxt *bp)
>                 }
>         }
>
> -       for (j = 0; j < bp->rx_nr_rings; j++) {
> -               struct bnxt_rx_queue *rxq = bp->rx_queues[j];
> -
> -               if (!rxq->rx_deferred_start) {
> -                       bp->eth_dev->data->rx_queue_state[j] =
> -                               RTE_ETH_QUEUE_STATE_STARTED;
> -                       rxq->rx_started = true;
> -               }
> -       }
> -
>         rc = bnxt_hwrm_cfa_l2_set_rx_mask(bp, &bp->vnic_info[0], 0, NULL);
>         if (rc) {
>                 PMD_DRV_LOG(ERR,
> --
> 2.10.1
>

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  5:14 Kalesh A P
2021-10-27  1:47 ` 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='CACZ4nhubUTbP2aEnWTYTSd12ChDy0kUGekn002sKkb57jQq=8w@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=kalesh-anakkur.purayil@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).