From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Cc: Pravin Pathak <pravin.pathak@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
"mike.ximing.chen@intel.com" <mike.ximing.chen@intel.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"nipun.gupta@amd.com" <nipun.gupta@amd.com>,
"chenbox@nvidia.com" <chenbox@nvidia.com>,
"tirthendu.sarkar@intel.com" <tirthendu.sarkar@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v1] app/eventdev: fix number of releases sent during cleanup
Date: Thu, 26 Jun 2025 22:56:10 +0530 [thread overview]
Message-ID: <CALBAE1MGDwtb_DUsB58KA2p32qkYr3e4aVQhaR5U=-9R=G8iQw@mail.gmail.com> (raw)
In-Reply-To: <PH0PR18MB408634F09235215A9DC29685DE78A@PH0PR18MB4086.namprd18.prod.outlook.com>
On Tue, Jun 24, 2025 at 11:57 AM Pavan Nikhilesh Bhagavatula
<pbhagavatula@marvell.com> wrote:
>
> >During cleanup, only send releases for events app was
> >not able to enqueue. Current code is sending releases for
> >entire dequeue burst.
> >
> >Fixes: f0b68c0b2af7 ("app/eventdev: clean up worker state before exit")
> >Cc: stable@dpdk.org
> >
> >Signed-off-by: Pravin Pathak <pravin.pathak@intel.com>
>
> Acked-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Applied to dpdk-next-eventdev/for-main. Thanks
>
> >---
> > app/test-eventdev/test_perf_common.c | 4 ++--
> > app/test-eventdev/test_pipeline_common.c | 4 ++--
> > 2 files changed, 4 insertions(+), 4 deletions(-)
> >
prev parent reply other threads:[~2025-06-26 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 18:13 Pravin Pathak
2025-06-24 6:21 ` Pavan Nikhilesh Bhagavatula
2025-06-26 17:26 ` 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='CALBAE1MGDwtb_DUsB58KA2p32qkYr3e4aVQhaR5U=-9R=G8iQw@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mike.ximing.chen@intel.com \
--cc=nipun.gupta@amd.com \
--cc=pbhagavatula@marvell.com \
--cc=pravin.pathak@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=tirthendu.sarkar@intel.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).