DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
	 "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 1/2] event/sw: add self tests to fast tests
Date: Tue, 3 Oct 2023 11:53:22 +0530	[thread overview]
Message-ID: <CALBAE1PRabmhhW2=-oC96pfw7Eq1fmkuS=JbsPBDBCxJTvYOqw@mail.gmail.com> (raw)
In-Reply-To: <20230928151428.895642-2-bruce.richardson@intel.com>

On Thu, Sep 28, 2023 at 9:01 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> By reducing the iterations for the final stage of the self-test, the SW
> eventdev tests can be fast enough for consideration in the fast-tests
> suite. This enables them to be run as part of the regular patch CI
> tests, and therefore increases the chances of catching any errors in
> patches that may affect this component.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>

Looks like  --to-cmd ./scripts/get_maintainer.pl not used in sending patches.
@Van Haaren, Harry  Could you review and Ack it to merge?


> ---
>  app/test/test_eventdev.c             | 2 +-
>  drivers/event/sw/sw_evdev_selftest.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/app/test/test_eventdev.c b/app/test/test_eventdev.c
> index c51c93bdbd..c94c15bef1 100644
> --- a/app/test/test_eventdev.c
> +++ b/app/test/test_eventdev.c
> @@ -1259,7 +1259,7 @@ test_eventdev_selftest_cn10k(void)
>  REGISTER_FAST_TEST(eventdev_common_autotest, true, true, test_eventdev_common);
>
>  #ifndef RTE_EXEC_ENV_WINDOWS
> -REGISTER_DRIVER_TEST(eventdev_selftest_sw, test_eventdev_selftest_sw);
> +REGISTER_FAST_TEST(eventdev_selftest_sw, true, true, test_eventdev_selftest_sw);
>  REGISTER_DRIVER_TEST(eventdev_selftest_octeontx, test_eventdev_selftest_octeontx);
>  REGISTER_TEST_COMMAND(eventdev_selftest_dpaa2, test_eventdev_selftest_dpaa2);
>  REGISTER_TEST_COMMAND(eventdev_selftest_dlb2, test_eventdev_selftest_dlb2);
> diff --git a/drivers/event/sw/sw_evdev_selftest.c b/drivers/event/sw/sw_evdev_selftest.c
> index 3aa8d76ca8..3f0d9806f2 100644
> --- a/drivers/event/sw/sw_evdev_selftest.c
> +++ b/drivers/event/sw/sw_evdev_selftest.c
> @@ -28,7 +28,7 @@
>
>  #define MAX_PORTS 16
>  #define MAX_QIDS 16
> -#define NUM_PACKETS (1<<18)
> +#define NUM_PACKETS (1 << 17)
>  #define DEQUEUE_DEPTH 128
>
>  static int evdev;
> --
> 2.39.2
>

  reply	other threads:[~2023-10-03  6:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 15:14 [PATCH 0/2] Add eventdev tests to test suites Bruce Richardson
2023-09-28 15:14 ` [PATCH 1/2] event/sw: add self tests to fast tests Bruce Richardson
2023-10-03  6:23   ` Jerin Jacob [this message]
2023-10-03  8:26     ` Van Haaren, Harry
2023-09-28 15:14 ` [PATCH 2/2] event/*: add driver selftests to driver-tests suite Bruce Richardson
2023-09-29 14:22 ` [PATCH 0/2] Add eventdev tests to test suites David Marchand
2023-10-03 10:02   ` Jerin Jacob

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='CALBAE1PRabmhhW2=-oC96pfw7Eq1fmkuS=JbsPBDBCxJTvYOqw@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@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).