From: Jerin Jacob <jerinjacobk@gmail.com>
To: Rashmi Shetty <rashmi.shetty@intel.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: dpdk-dev <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>,
pravin.pathak@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] app/test-eventdev: add burst enqueue support
Date: Thu, 14 Oct 2021 12:00:29 +0530 [thread overview]
Message-ID: <CALBAE1M9ESF97y7OwY33joS83CxX-gU0_sM9pbUm5QyPAq1Hmw@mail.gmail.com> (raw)
In-Reply-To: <20211013201602.113694-1-rashmi.shetty@intel.com>
On Thu, Oct 14, 2021 at 1:46 AM Rashmi Shetty <rashmi.shetty@intel.com> wrote:
>
> This commit introduces a new command line option prod_enq_burst_sz
> to set burst size for eventdev enqueue at producer in perf_queue
> test. The newly added function perf_producer_burst is called when
> prod_enq_burst_sz is greater than 1.
>
> Signed-off-by: Rashmi Shetty <rashmi.shetty@intel.com>
> ---
> app/test-eventdev/evt_common.h | 1 +
> app/test-eventdev/evt_main.c | 2 +-
> app/test-eventdev/evt_options.c | 14 +++++
> app/test-eventdev/evt_options.h | 1 +
> app/test-eventdev/test_perf_common.c | 81 +++++++++++++++++++++++++++-
> app/test-eventdev/test_perf_common.h | 1 +
Update doc/guides/tools/testeventdev.rst for this new command-line option and
extended existing example command to use the new one as a separate command.
> 6 files changed, 97 insertions(+), 3 deletions(-)
>
> diff --git a/app/test-eventdev/evt_common.h b/app/test-eventdev/evt_common.h
> index 28afb114b3..f466434459 100644
> + struct perf_elt *m[MAX_PROD_ENQ_BURST_SIZE + 1] = {NULL};
Use memcpy, some old compiler may issue with this kind of usage.
> + struct rte_event ev[MAX_PROD_ENQ_BURST_SIZE + 1];
> + uint32_t burst_size = opt->prod_enq_burst_sz;
> +
> + rte_event_dev_info_get(dev_id, &dev_info);
> + if (dev_info.max_event_port_enqueue_depth < burst_size)
> + burst_size = dev_info.max_event_port_enqueue_depth;
> +
> + if (opt->verbose_level > 1)
> + printf("%s(): lcore %d dev_id %d port=%d queue %d\n", __func__,
> + rte_lcore_id(), dev_id, port, p->queue_id);
> +
prev parent reply other threads:[~2021-10-14 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 21:05 [dpdk-dev] [PATCH] app/test-eventdev: add burst enqueue support in perf_queue test Rashmi Shetty
2021-10-13 20:16 ` [dpdk-dev] [PATCH v2] app/test-eventdev: add burst enqueue support Rashmi Shetty
2021-10-14 6:30 ` 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=CALBAE1M9ESF97y7OwY33joS83CxX-gU0_sM9pbUm5QyPAq1Hmw@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=pravin.pathak@intel.com \
--cc=rashmi.shetty@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).