DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: rushilg@google.com, joshwash@google.com, dev@dpdk.org
Subject: Re: [PATCH] net/gve: Update TX queue state
Date: Mon, 22 Jul 2024 19:49:08 +0530	[thread overview]
Message-ID: <CA++LmPU+=T67a-jH-qAEkjFY4WQETzn3OM5EwAj1yj_xi6n41A@mail.gmail.com> (raw)
In-Reply-To: <ba12c63b-fc0f-444f-9455-aacc4642f2a8@amd.com>

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

Thanks Ferruh.

On Mon, Jul 22, 2024 at 7:41 PM Ferruh Yigit <ferruh.yigit@amd.com> wrote:

> On 7/22/2024 12:10 PM, Tathagat Priyadarshi wrote:
> > Fixing Typo in updating the TX queue state
> >
> > Signed-off-by: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
> >
>
> Good catch, thanks Tathagat.
>
> I think impact is more than just typo, so let me update the patch title as:
>
> net/gve: fix Tx queue state on queue start
>
> Also needs fixes tag:
>  Fixes: b044845bb015 ("net/gve: support queue start/stop")
>  Cc: stable@dpdk.org
>
> With above changes,
> Reviewed-by: Ferruh Yigit <ferruh.yigit@amd.com>
>
> Applied to dpdk-next-net/main, thanks.
>
> > ---
> >  drivers/net/gve/gve_tx.c     | 2 +-
> >  drivers/net/gve/gve_tx_dqo.c | 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/net/gve/gve_tx.c b/drivers/net/gve/gve_tx.c
> > index 70d3ef0..500ae31 100644
> > --- a/drivers/net/gve/gve_tx.c
> > +++ b/drivers/net/gve/gve_tx.c
> > @@ -688,7 +688,7 @@
> >
> >       rte_write32(rte_cpu_to_be_32(GVE_IRQ_MASK), txq->ntfy_addr);
> >
> > -     dev->data->rx_queue_state[tx_queue_id] =
> RTE_ETH_QUEUE_STATE_STARTED;
> > +     dev->data->tx_queue_state[tx_queue_id] =
> RTE_ETH_QUEUE_STATE_STARTED;
> >
> >       return 0;
> >  }
> > diff --git a/drivers/net/gve/gve_tx_dqo.c b/drivers/net/gve/gve_tx_dqo.c
> > index a65e6aa..1b85557 100644
> > --- a/drivers/net/gve/gve_tx_dqo.c
> > +++ b/drivers/net/gve/gve_tx_dqo.c
> > @@ -392,7 +392,7 @@
> >
> >       rte_write32(rte_cpu_to_be_32(GVE_IRQ_MASK), txq->ntfy_addr);
> >
> > -     dev->data->rx_queue_state[tx_queue_id] =
> RTE_ETH_QUEUE_STATE_STARTED;
> > +     dev->data->tx_queue_state[tx_queue_id] =
> RTE_ETH_QUEUE_STATE_STARTED;
> >
> >       return 0;
> >  }
>
>

[-- Attachment #2: Type: text/html, Size: 2593 bytes --]

      reply	other threads:[~2024-07-22 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-22 11:10 Tathagat Priyadarshi
2024-07-22 14:11 ` Ferruh Yigit
2024-07-22 14:19   ` Tathagat Priyadarshi [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='CA++LmPU+=T67a-jH-qAEkjFY4WQETzn3OM5EwAj1yj_xi6n41A@mail.gmail.com' \
    --to=tathagat.dpdk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=joshwash@google.com \
    --cc=rushilg@google.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).