DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Anoob Joseph <anoobj@marvell.com>,
	Declan Doherty <declan.doherty@intel.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: Abhinandan Gujjar <abhinandan.gujjar@intel.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Tiwei Bie <tiwei.bie@intel.com>,
	Zhihong Wang <zhihong.wang@intel.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	Radu Nicolau <radu.nicolau@intel.com>,
	Fiona Trahe <fiona.trahe@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Narayana Prasad <pathreya@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] cryptodev: add ff_disable field in cryptodev config
Date: Tue, 25 Jun 2019 10:20:20 +0000	[thread overview]
Message-ID: <VE1PR04MB66396F56BBB3D86549ACC603E6E30@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1561441164-11958-1-git-send-email-anoobj@marvell.com>


> 
> 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.
> 
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> ---
> v2:
> * Updated test & example applications to incorporate the default setting
>   for ff_disable field. Disabling SECURITY offload for cases where only
>   crypto is applicable & asymmetric crypto in case of ipsec etc.
> 
>  app/test-crypto-perf/main.c                   |  3 ++-
>  app/test/test_cryptodev.c                     |  2 ++
>  app/test/test_event_crypto_adapter.c          |  1 +
>  app/test/test_ipsec.c                         |  1 +
>  doc/guides/rel_notes/deprecation.rst          | 14 --------------
>  doc/guides/rel_notes/release_19_08.rst        | 11 ++++++++++-
>  examples/fips_validation/fips_dev_self_test.c |  6 +++++-
>  examples/fips_validation/main.c               |  2 +-
>  examples/ip_pipeline/cryptodev.c              |  1 +
>  examples/ipsec-secgw/ipsec-secgw.c            |  1 +
>  examples/l2fwd-crypto/main.c                  |  1 +
>  examples/vhost_crypto/main.c                  |  1 +
>  lib/librte_cryptodev/Makefile                 |  2 +-
>  lib/librte_cryptodev/meson.build              |  2 +-
>  lib/librte_cryptodev/rte_cryptodev.h          |  7 +++++++
>  15 files changed, 35 insertions(+), 20 deletions(-)
> 
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

  reply	other threads:[~2019-06-25 10:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 15:25 [dpdk-dev] [PATCH] " Anoob Joseph
2019-06-20 14:06 ` Akhil Goyal
2019-06-21 13:10 ` Akhil Goyal
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 [this message]
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=VE1PR04MB66396F56BBB3D86549ACC603E6E30@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=abhinandan.gujjar@intel.com \
    --cc=anoobj@marvell.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=jerinj@marvell.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=pathreya@marvell.com \
    --cc=radu.nicolau@intel.com \
    --cc=tiwei.bie@intel.com \
    --cc=zhihong.wang@intel.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).