From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [EXT] [PATCH] test/eventdev: avoid configuring port or queue twice
Date: Fri, 10 Nov 2023 12:49:29 +0530 [thread overview]
Message-ID: <CALBAE1PGVSwmLWF9qS+K5a5fd=TWs=DOhnOEEwzvfPmoh5uF5A@mail.gmail.com> (raw)
In-Reply-To: <PH0PR18MB4086D55D57BAAA9D72A2CB9BDEA9A@PH0PR18MB4086.namprd18.prod.outlook.com>
On Wed, Nov 8, 2023 at 12:22 AM Pavan Nikhilesh Bhagavatula
<pbhagavatula@marvell.com> wrote:
>
>
> > In the basic sanity tests of eventdev for queue and port setup, queue 0
> > was configured separately before running a loop to configure the rest of
> > the queues. This loop started from 0, so reconfigured queue 0, and a
> > similar reconfiguration happens with port 0 in the later port setup
> > test. While most eventdevs should handle this reconfiguration without
> > stop/start correctly, it can cause issues, and should be tested
> > separately from basic config tests.
> >
> > Therefore, adjust loops to start at 1 rather than 0 and avoid
> > configuring queue 0 and port 0 twice.
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>
> Acked-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-eventdev/for-main. Thanks
prev parent reply other threads:[~2023-11-10 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 16:39 Bruce Richardson
2023-11-07 17:35 ` [EXT] " Pavan Nikhilesh Bhagavatula
2023-11-10 7:19 ` 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='CALBAE1PGVSwmLWF9qS+K5a5fd=TWs=DOhnOEEwzvfPmoh5uF5A@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=bruce.richardson@intel.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).