> > > > > 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 <ano...@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.go...@nxp.com>
Applied to dpdk-next-crypto Thanks.
