patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: Shijith Thotton <sthotton@marvell.com>,
	Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
	dpdk stable <stable@dpdk.org>
Subject: Re: [PATCH] event/cnxk: fix incorrect return value
Date: Mon, 13 Jun 2022 11:27:44 +0530	[thread overview]
Message-ID: <CALBAE1NGQeetg+sMXYbf_6ggGryp2DOzSexR1vVyAwqWWS8r7A@mail.gmail.com> (raw)
In-Reply-To: <20220518140411.5284-1-pbhagavatula@marvell.com>

On Wed, May 18, 2022 at 7:34 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> The `rte_event_eth_tx_adapter_enqueue()` function expects driver layer
> to return the total number of events successfully transmitted.
> Fix cn10k driver returning the number of packets transmitted in a
> event vector instead of number of events.
>
> Fixes: 761a321acf91 ("event/cnxk: support vectorized Tx event fast path")
> Cc: stable@dpdk.org
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>

Applied to dpdk-next-net-eventdev/for-main. Thanks


> ---
>  drivers/event/cnxk/cn10k_worker.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/event/cnxk/cn10k_worker.h b/drivers/event/cnxk/cn10k_worker.h
> index 034f508dd8..0915f404e0 100644
> --- a/drivers/event/cnxk/cn10k_worker.h
> +++ b/drivers/event/cnxk/cn10k_worker.h
> @@ -651,7 +651,7 @@ cn10k_sso_hws_event_tx(struct cn10k_sso_hws *ws, struct rte_event *ev,
>                 }
>                 rte_mempool_put(rte_mempool_from_obj(ev->vec), ev->vec);
>                 rte_prefetch0(ws);
> -               return (meta & 0xFFFF);
> +               return 1;
>         }
>
>         m = ev->mbuf;
> --
> 2.25.1
>

      reply	other threads:[~2022-06-13  5:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 14:04 pbhagavatula
2022-06-13  5:57 ` Jerin Jacob [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=CALBAE1NGQeetg+sMXYbf_6ggGryp2DOzSexR1vVyAwqWWS8r7A@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=stable@dpdk.org \
    --cc=sthotton@marvell.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).