From: Akhil Goyal <akhil.goyal@nxp.com>
To: Anoob Joseph <anoobj@marvell.com>,
Declan Doherty <declan.doherty@intel.com>,
Fiona Trahe <fiona.trahe@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Jerin Jacob <jerinj@marvell.com>, Narayana Prasad <pathreya@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: add ff_disable field in cryptodev config
Date: Fri, 21 Jun 2019 13:10:20 +0000 [thread overview]
Message-ID: <VE1PR04MB66393F897CBDA57AD5D42375E6E70@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1559575528-5363-1-git-send-email-anoobj@marvell.com>
Hi Anoob,
>
> Adding a new field, ff_disable, to allow applications to control the
> features enabled on the crypto device. This would allow for efficient
> usage of HW/SW offloads by disabling the features not required by the
> application.
>
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
I see a compilation issue with this change.
/home/akhil/up/dpdk-next-crypto/examples/fips_validation/fips_dev_self_test.c: In function 'fips_dev_auto_test_init':
/home/akhil/up/dpdk-next-crypto/examples/fips_validation/fips_dev_self_test.c:1560:9: error: missing initializer for field 'ff_disable' of 'struct rte_cryptodev_config' [-Werror=missing-field-initializers]
struct rte_cryptodev_config conf = {rte_cryptodev_socket_id(dev_id), 1};
^~~~~~~~~~~~~~~~~~~~
In file included from /home/akhil/up/dpdk-next-crypto/examples/fips_validation/fips_dev_self_test.c:5:0:
/home/akhil/up/dpdk-next-crypto/arm64-dpaa-linuxapp-gcc/include/rte_cryptodev.h:615:11: note: 'ff_disable' declared here
uint64_t ff_disable;
^~~~~~~~~~
Please add a patch for all applications which use struct rte_cryptodev_config and set the default values of its parameters.
> ---
> doc/guides/rel_notes/deprecation.rst | 14 --------------
> doc/guides/rel_notes/release_19_08.rst | 11 ++++++++++-
> lib/librte_cryptodev/Makefile | 2 +-
> lib/librte_cryptodev/meson.build | 2 +-
> lib/librte_cryptodev/rte_cryptodev.h | 7 +++++++
> 5 files changed, 19 insertions(+), 17 deletions(-)
>
next prev parent reply other threads:[~2019-06-21 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 15:25 Anoob Joseph
2019-06-20 14:06 ` Akhil Goyal
2019-06-21 13:10 ` Akhil Goyal [this message]
2019-06-24 3:40 ` [dpdk-dev] [EXT] " Anoob Joseph
2019-06-25 5:39 ` [dpdk-dev] [PATCH v2] " Anoob Joseph
2019-06-25 10:20 ` Akhil Goyal
2019-06-25 12:42 ` 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=VE1PR04MB66393F897CBDA57AD5D42375E6E70@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=declan.doherty@intel.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 \
/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).