From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
Anoob Joseph <anoobj@marvell.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Narayana Prasad Raju Athreya <pathreya@marvell.com>,
Shally Verma <shallyv@marvell.com>,
Suheil Chandran <schandran@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce ABI change for cryptodev config
Date: Fri, 29 Mar 2019 14:23:05 +0000 [thread overview]
Message-ID: <882fb8af-e823-4d50-6b2a-c3ae4c33f54e@nxp.com> (raw)
Message-ID: <20190329142305.r72p8SVS7xYSGmKbhH7NnfEO9sV97kJuBduZsK5kJ60@z> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B4358970DBDF@IRSMSX101.ger.corp.intel.com>
On 3/7/2019 8:55 PM, Trahe, Fiona wrote:
>
>> -----Original Message-----
>> From: Anoob Joseph [mailto:anoobj@marvell.com]
>> Sent: Thursday, March 7, 2019 10:40 AM
>> To: Akhil Goyal <akhil.goyal@nxp.com>; Trahe, Fiona <fiona.trahe@intel.com>; De Lara Guarch, Pablo
>> <pablo.de.lara.guarch@intel.com>
>> Cc: Anoob Joseph <anoobj@marvell.com>; Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Narayana
>> Prasad Raju Athreya <pathreya@marvell.com>; Shally Verma <shallyv@marvell.com>; Suheil Chandran
>> <schandran@marvell.com>; dev@dpdk.org
>> Subject: [PATCH v2] doc: announce ABI change for cryptodev config
>>
>> Add new field ff_disable in rte_cryptodev_config. This enables
>> applications to control the features enabled on the crypto device.
>>
>> Proposed new layout:
>>
>> /** Crypto device configuration structure */
>> struct rte_cryptodev_config {
>> int socket_id; /**< Socket to allocate resources on */
>> uint16_t nb_queue_pairs;
>> /**< Number of queue pairs to configure on device */
>> + uint64_t ff_disable;
>> + /**< Feature flags to be disabled. Only the following features are
>> + * allowed to be disabled,
>> + * - RTE_CRYPTODEV_FF_SYMMETRIC_CRYPTO
>> + * - RTE_CRYPTODEV_FF_ASYMMETRIC_CRYPTO
>> + * - RTE_CRYTPODEV_FF_SECURITY
>> + */
>> };
>>
>> For eth devices, rte_eth_conf.rx_mode.offloads and
>> rte_eth_conf.tx_mode.offloads fields are used by applications to
>> control the offloads enabled on the eth device. This proposal adds a
>> similar ability for the crypto device.
>>
>> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> Acked-by: Fiona Trahe <fiona.trahe@intel.com>
>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Applied to dpdk-next-crypto
Thanks.
next prev parent reply other threads:[~2019-03-29 14:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 9:39 [dpdk-dev] [PATCH] " Anoob Joseph
2019-01-17 11:37 ` Trahe, Fiona
2019-01-17 13:47 ` Anoob Joseph
2019-01-18 6:59 ` Shally Verma
2019-01-22 9:31 ` Anoob Joseph
2019-01-31 9:53 ` Akhil Goyal
2019-02-01 11:14 ` Thomas Monjalon
2019-02-01 11:49 ` Trahe, Fiona
2019-02-28 10:02 ` Akhil Goyal
2019-02-28 10:54 ` Anoob Joseph
2019-03-07 10:39 ` [dpdk-dev] [PATCH v2] " Anoob Joseph
2019-03-07 15:25 ` Trahe, Fiona
2019-03-29 14:23 ` Akhil Goyal [this message]
2019-03-29 14:23 ` Akhil Goyal
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=882fb8af-e823-4d50-6b2a-c3ae4c33f54e@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=jerinj@marvell.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=pathreya@marvell.com \
--cc=schandran@marvell.com \
--cc=shallyv@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).