From: "Kumar, Ravi1" <Ravi1.Kumar@amd.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v2] crypto/ccp: support command line option to enable CPU based auth
Date: Thu, 10 May 2018 08:43:08 +0000 [thread overview]
Message-ID: <CY4PR12MB150916599449E58611747C8FAE980@CY4PR12MB1509.namprd12.prod.outlook.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CD05715@IRSMSX108.ger.corp.intel.com>
>Hi Ravi,
>
>> -----Original Message-----
>> From: Ravi Kumar [mailto:Ravi1.kumar@amd.com]
>> Sent: Wednesday, May 9, 2018 1:46 PM
>> To: dev@dpdk.org
>> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
>> thomas@monjalon.net; hemant.agrawal@nxp.com
>> Subject: [PATCH v2] crypto/ccp: support command line option to enable
>> CPU based auth
>>
>> CCP PMD supports authentication offload to either of CCP or CPU.
>> The earlier version of patch provides this option as compile time.
>> This patch changes this option from compile time to run time.
>> User can pass "ccp_auth_opt=1" as an additional arguments to vdev
>> parameter to enable authentication operations on CPU.
>>
>> Signed-off-by: Ravi Kumar <Ravi1.kumar@amd.com>
>
>...
>
>> RTE_PMD_REGISTER_VDEV(CRYPTODEV_NAME_CCP_PMD,
>> cryptodev_ccp_pmd_drv);
>> RTE_PMD_REGISTER_PARAM_STRING(CRYPTODEV_NAME_CCP_PMD,
>> - "max_nb_queue_pairs=<int> max_nb_sessions=<int> socket_id=<int>");
>> + "max_nb_queue_pairs=<int> "
>> + "max_nb_sessions=<int> "
>> + "socket_id=<int> "
>> + "ccp_auth_opt=<int>");
>
>
>Die_num is not in this list. I was going to add it myself, but then I realized that it is not actually used anywhere.
>Am I missing something?
>
>Also, I think it is worth updating the documentation of the PMD with these parameters.
>
>Thanks,
>Pablo
>
Hi Pablo,
Die-num parameter is going to be used in future. Will remove for now and send an updated patch.
Thanks,
Ravi
next prev parent reply other threads:[~2018-05-10 8:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 5:57 [dpdk-dev] [PATCH 1/2] crypto/ccp: enable CCP crypto poll mode driver by default Ravi Kumar
2018-05-03 5:57 ` [dpdk-dev] [PATCH 2/2] crypto/ccp: change to command line option from compile time Ravi Kumar
2018-05-09 8:34 ` De Lara Guarch, Pablo
2018-05-03 7:23 ` [dpdk-dev] [PATCH 1/2] crypto/ccp: enable CCP crypto poll mode driver by default De Lara Guarch, Pablo
2018-05-09 5:53 ` Kumar, Ravi1
2018-05-09 7:58 ` Thomas Monjalon
2018-05-09 8:11 ` Kumar, Ravi1
2018-05-09 8:19 ` Thomas Monjalon
2018-05-09 8:36 ` De Lara Guarch, Pablo
2018-05-09 8:58 ` Kumar, Ravi1
2018-05-09 12:46 ` [dpdk-dev] [PATCH v2] crypto/ccp: support command line option to enable CPU based auth Ravi Kumar
2018-05-09 15:27 ` De Lara Guarch, Pablo
2018-05-10 8:43 ` Kumar, Ravi1 [this message]
2018-05-10 8:46 ` De Lara Guarch, Pablo
2018-05-10 9:20 ` [dpdk-dev] [PATCH v3] " Ravi Kumar
2018-05-10 12:22 ` De Lara Guarch, Pablo
2018-05-11 5:37 ` Kumar, Ravi1
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=CY4PR12MB150916599449E58611747C8FAE980@CY4PR12MB1509.namprd12.prod.outlook.com \
--to=ravi1.kumar@amd.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas@monjalon.net \
/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).