DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com, dev@dpdk.org
Subject: Re: [PATCH] app/eventdev: fix incorrect cleanup check
Date: Wed, 28 Sep 2022 19:20:53 +0530	[thread overview]
Message-ID: <CALBAE1PDqJ6JZi3V0dDxWLmLLf10UNJ9rr-QOaLU7YAEGfAwzA@mail.gmail.com> (raw)
In-Reply-To: <20220926150548.5076-1-pbhagavatula@marvell.com>

On Mon, Sep 26, 2022 at 8:35 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> During cleanup `rte_event_port_quiesce` should be called
> irrespective of whether an event has been dequeued or not
> to flush any prefetched events.
>
> Fixes: 7da008df0c8d ("app/eventdev: use port quiescing")
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>

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


> ---
>  app/test-eventdev/test_pipeline_common.c | 3 ---
>  1 file changed, 3 deletions(-)
>
> diff --git a/app/test-eventdev/test_pipeline_common.c b/app/test-eventdev/test_pipeline_common.c
> index 4f40d37659..22a3918ed8 100644
> --- a/app/test-eventdev/test_pipeline_common.c
> +++ b/app/test-eventdev/test_pipeline_common.c
> @@ -696,9 +696,6 @@ pipeline_worker_cleanup(uint8_t dev, uint8_t port, struct rte_event ev[],
>  {
>         int i;
>
> -       if (!(deq - enq))
> -               return;
> -
>         if (deq) {
>                 for (i = enq; i < deq; i++) {
>                         if (ev[i].op == RTE_EVENT_OP_RELEASE)
> --
> 2.25.1
>

      reply	other threads:[~2022-09-28 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 15:05 pbhagavatula
2022-09-28 13:50 ` 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=CALBAE1PDqJ6JZi3V0dDxWLmLLf10UNJ9rr-QOaLU7YAEGfAwzA@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@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).