From: Jerin Jacob <jerinjacobk@gmail.com>
To: Akhil Goyal <gakhil@marvell.com>
Cc: Aakash Sasidharan <asasidharan@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"akhil@marvell.com" <akhil@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Volodymyr Fialko <vfialko@marvell.com>,
Shijith Thotton <sthotton@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [EXT] [PATCH] app/testeventdev: add cipher alg option for cryptodev
Date: Fri, 3 Mar 2023 21:01:04 +0530 [thread overview]
Message-ID: <CALBAE1MKgoUu_0gTuSE5MS_JE_G47qgBsNEsmJXrxBzON-K2Ow@mail.gmail.com> (raw)
In-Reply-To: <CO6PR18MB4484BFA1049E8965CE3CFC62D8AF9@CO6PR18MB4484.namprd18.prod.outlook.com>
On Mon, Feb 27, 2023 at 10:06 PM Akhil Goyal <gakhil@marvell.com> wrote:
>
> > Testeventdev crypto adapter symmetric tests are only attempting
> > NULL cipher algorithm. This limits crypto adapter usage with only
> > PMDs that can support NULL cipher algorithm. Also, since NULL cipher
> > algorithm doesn't perform any crypto operation, the performance numbers
> > reported may not reflect the actual crypto capabilities of the device.
> > Extend the application to support non-NULL cipher algorithms.
> >
> > Signed-off-by: Aakash Sasidharan <asasidharan@marvell.com>
> Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-net-eventdev/for-main with following changes. Thanks
1) Changed subject as "app/testeventdev: support cipher alg options
for cryptodev"
2) Updated the doc as
diff --git a/doc/guides/tools/testeventdev.rst
b/doc/guides/tools/testeventdev.rst
index 33cbe04d70..fc36bfb30c 100644
--- a/doc/guides/tools/testeventdev.rst
+++ b/doc/guides/tools/testeventdev.rst
@@ -162,6 +162,18 @@ The following are the application command-line options:
Set crypto operation type. Use 0 for symmetric crypto ops (default)
and 1 for asymmetric crypto ops.
+* ``--crypto_cipher_alg``
+
+ Cipher algorithm to be used. Default algorithm is NULL.
+
+* ``--crypto_cipher_key``
+
+ Key for the cipher algorithm selected.
+
+* ``--crypto_cipher_iv_sz``
+
+ IV size for the cipher algorithm
+
* ``--mbuf_sz``
Set packet mbuf size. Can be used to configure Jumbo Frames. Only
[for-main]dell[dpdk-next-eventdev]
prev parent reply other threads:[~2023-03-03 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 14:11 Aakash Sasidharan
2023-02-27 16:35 ` [EXT] " Akhil Goyal
2023-03-03 15:31 ` 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=CALBAE1MKgoUu_0gTuSE5MS_JE_G47qgBsNEsmJXrxBzON-K2Ow@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=akhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=asasidharan@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=sthotton@marvell.com \
--cc=vfialko@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).