From: Jerin Jacob <jerinjacobk@gmail.com>
To: Amit Prakash Shukla <amitprakashs@marvell.com>
Cc: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
Jerin Jacob <jerinj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] test/event: fix incorrect target event queue
Date: Wed, 18 Sep 2024 13:43:16 +0530 [thread overview]
Message-ID: <CALBAE1MOAci8WCkndWJm_kYQVNkScR2Zbym5Cr9YZj2Bkj8DtA@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR18MB516176F79F5F472421B95FE5C88F2@SJ0PR18MB5161.namprd18.prod.outlook.com>
On Thu, Aug 22, 2024 at 1:31 PM Amit Prakash Shukla
<amitprakashs@marvell.com> wrote:
>
> > -----Original Message-----
> > From: pbhagavatula@marvell.com <pbhagavatula@marvell.com>
> > Sent: Thursday, August 22, 2024 2:08 AM
> > To: Jerin Jacob <jerinj@marvell.com>; Amit Prakash Shukla
> > <amitprakashs@marvell.com>
> > Cc: dev@dpdk.org; Pavan Nikhilesh Bhagavatula
> > <pbhagavatula@marvell.com>
> > Subject: [PATCH] test/event: fix incorrect target event queue
> >
> > From: Pavan Nikhilesh <pbhagavatula@marvell.com>
> >
> > In OP_FWD mode, if internal port is supported, the target event queue should
> > be the TEST_APP_EV_QUEUE_ID.
> >
> > Fixes: a276e7c8fbb3 ("test/event: add DMA adapter auto-test")
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> > ---
> > app/test/test_event_dma_adapter.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
>
> Tested-by: Amit Prakash Shukla <amitprakashs@marvell.com>
> Acked-by: Amit Prakash Shukla <amitprakashs@marvell.com>
Applied to dpdk-next-eventdev/for-main. Thanks
> Thanks.
>
> >
> > diff --git a/app/test/test_event_dma_adapter.c
> > b/app/test/test_event_dma_adapter.c
> > index 3b39521153bb..9988d4fc7bc5 100644
> > --- a/app/test/test_event_dma_adapter.c
> > +++ b/app/test/test_event_dma_adapter.c
> > @@ -271,7 +271,10 @@ test_op_forward_mode(void)
> > ev[i].event = 0;
> > ev[i].op = RTE_EVENT_OP_NEW;
> > ev[i].event_type = RTE_EVENT_TYPE_DMADEV;
> > - ev[i].queue_id = TEST_DMA_EV_QUEUE_ID;
> > + if (params.internal_port_op_fwd)
> > + ev[i].queue_id = TEST_APP_EV_QUEUE_ID;
> > + else
> > + ev[i].queue_id = TEST_DMA_EV_QUEUE_ID;
> > ev[i].sched_type = RTE_SCHED_TYPE_ATOMIC;
> > ev[i].flow_id = 0xAABB;
> > ev[i].event_ptr = op;
> > --
> > 2.45.2
>
prev parent reply other threads:[~2024-09-18 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 20:37 pbhagavatula
2024-08-22 8:01 ` Amit Prakash Shukla
2024-09-18 8:13 ` 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=CALBAE1MOAci8WCkndWJm_kYQVNkScR2Zbym5Cr9YZj2Bkj8DtA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=amitprakashs@marvell.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).