From: Volodymyr Fialko <vfialko@marvell.com>
To: Volodymyr Fialko <vfialko@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: Anoob Joseph <anoobj@marvell.com>, Akhil Goyal <gakhil@marvell.com>
Subject: RE: [PATCH] app/testeventdev: add vector worker to perf test
Date: Tue, 6 Dec 2022 09:27:32 +0000 [thread overview]
Message-ID: <MW2PR18MB2282912DBE585875315610A1A81B9@MW2PR18MB2282.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221202101139.1522945-1-vfialko@marvell.com>
> -----Original Message-----
> From: Volodymyr Fialko <vfialko@marvell.com>
> Sent: Friday, December 2, 2022 11:12 AM
> To: dev@dpdk.org; Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> Cc: Anoob Joseph <anoobj@marvell.com>; Akhil Goyal <gakhil@marvell.com>; Volodymyr Fialko
> <vfialko@marvell.com>
> Subject: [PATCH] app/testeventdev: add vector worker to perf test
>
> Add worker for handling vector events to perf tests, vector events could be generated by crypto adapter
> producer.
>
> Example:
> ./dpdk-test-eventdev -l 0-2 -a <EVENTDEV> -a <CRYPTODEV> -- \
> --prod_type_cryptodev --crypto_adptr_mode 1 --test=perf_queue \
> --stlist=a --wlcores 1 --plcores 2 --prod_enq_burst_sz 32 \
> --enable_vector --vector_tmo_ns 0 --nb_flows 2
>
> Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
> ---
Depens-on: series-26008 ("build: fix missing crypto vec limits in version")
next prev parent reply other threads:[~2022-12-06 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 10:11 Volodymyr Fialko
2022-12-06 9:27 ` Volodymyr Fialko [this message]
2023-01-17 15:29 ` [EXT] " Shijith Thotton
2023-01-24 11:53 ` 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=MW2PR18MB2282912DBE585875315610A1A81B9@MW2PR18MB2282.namprd18.prod.outlook.com \
--to=vfialko@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@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).