[dpdk-dev] [PATCH v5 0/6] Cryptodev API/ABI deprecation notices
Pablo de Lara
pablo.de.lara.guarch at intel.com
Mon May 21 15:08:35 CEST 2018
- Previous message: [dpdk-dev] [PATCH] net/liquidio:fix Unable to update lio_dev->linfo.link var When I was using VPP +dpdk-18.02+liqudio CN23xx, I encountered such a bug. When VPP called dpdk_device_start to initialize DPDK liqudio drive, I found that initialization failed. The reason for the failure is that VF MTU > PF MTU, but PF MTU has been modified to 9600 (> VF MTU). Finally, I am location that DPDK liqudio drive cannot get the correct PF driver to liqudio network card. It is due to the fact that when VPP calls dpdk_device_start to initialize DPDK liqudio drive, this time, lio_dev->linfo. Link var already exists in the old value, not empty. Cause lio_dev - > linfo. Link. Link_status64 != 0 statement is set up, and the link info is stopped directly to liqudio card, resulting in no get accurate pf mtu. I did a test model to reproduce the bug, which is to add rte_eth_dev_set_mtu(portid, vf_mtu) to the rte_eth_dev_start function when using dpdk-18.02+liqudio CN23xx+l2fwd. You need to make sure that 1500 < vf_mtu < pf_mtu will be available. At this time, you will have net_liovf[04:00.3]ERROR: lio_dev_mtu_set() VF MTU should be >= 68 and <= 1500. Such a mistake.
- Next message: [dpdk-dev] [PATCH v5 1/6] doc: announce ABI change for crypto sym info struct
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
v5:
- Renamed rte_cryptodev_get_header_session_size with
rte_cryptodev_sym_get_header_session_size, and
rte_cryptodev_get_private_session_size with
rte_cryptodev_sym_get_private_session_size.
v4:
- Fixed DPDK versions called out to deprecate/remove API.
- Removed rte_cryptodev_queue_pair_attach_sym_session call
from the IPSec gw app, since the function is deprecated now.
- Added patch announcing a replacement of some of the crypto
feature flags
- Added patch renaming two symmetric specific functions
from *_session_* to *_sym_session_*.
v3:
- Added an extra deprecation announcement (replacing rte_pci_device
with rte_device)
- Rebased against latest DPDK code
v2:
- Added an extra deprecation announcement
- Bonded the other two deprecation notices with the new one in a
patchset
Pablo de Lara (6):
doc: announce ABI change for crypto sym info struct
doc: announce ABI change for crypto info struct
doc: announce deprecation for attach/detach crypto session
doc: announce deprecation in crypto queue pair start/stop
doc: announce deprecation in crypto feature flags
cryptodev: rename get session size API
app/test-crypto-perf/main.c | 2 +-
doc/guides/prog_guide/cryptodev_lib.rst | 6 ++--
doc/guides/rel_notes/deprecation.rst | 25 +++++++++++++
drivers/crypto/aesni_gcm/aesni_gcm_pmd.c | 2 +-
drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 2 +-
drivers/crypto/armv8/rte_armv8_pmd.c | 2 +-
drivers/crypto/kasumi/rte_kasumi_pmd.c | 2 +-
drivers/crypto/openssl/rte_openssl_pmd.c | 2 +-
drivers/crypto/snow3g/rte_snow3g_pmd.c | 2 +-
drivers/crypto/zuc/rte_zuc_pmd.c | 2 +-
examples/ipsec-secgw/ipsec-secgw.c | 2 +-
examples/ipsec-secgw/ipsec.c | 12 -------
examples/l2fwd-crypto/main.c | 2 +-
examples/vhost_crypto/main.c | 2 +-
lib/librte_cryptodev/rte_cryptodev.c | 12 +++++++
lib/librte_cryptodev/rte_cryptodev.h | 35 +++++++++++++++++++
.../rte_cryptodev_version.map | 8 +++++
test/test/test_cryptodev.c | 6 ++--
test/test/test_event_crypto_adapter.c | 2 +-
19 files changed, 99 insertions(+), 29 deletions(-)
--
2.17.0
- Previous message: [dpdk-dev] [PATCH] net/liquidio:fix Unable to update lio_dev->linfo.link var When I was using VPP +dpdk-18.02+liqudio CN23xx, I encountered such a bug. When VPP called dpdk_device_start to initialize DPDK liqudio drive, I found that initialization failed. The reason for the failure is that VF MTU > PF MTU, but PF MTU has been modified to 9600 (> VF MTU). Finally, I am location that DPDK liqudio drive cannot get the correct PF driver to liqudio network card. It is due to the fact that when VPP calls dpdk_device_start to initialize DPDK liqudio drive, this time, lio_dev->linfo. Link var already exists in the old value, not empty. Cause lio_dev - > linfo. Link. Link_status64 != 0 statement is set up, and the link info is stopped directly to liqudio card, resulting in no get accurate pf mtu. I did a test model to reproduce the bug, which is to add rte_eth_dev_set_mtu(portid, vf_mtu) to the rte_eth_dev_start function when using dpdk-18.02+liqudio CN23xx+l2fwd. You need to make sure that 1500 < vf_mtu < pf_mtu will be available. At this time, you will have net_liovf[04:00.3]ERROR: lio_dev_mtu_set() VF MTU should be >= 68 and <= 1500. Such a mistake.
- Next message: [dpdk-dev] [PATCH v5 1/6] doc: announce ABI change for crypto sym info struct
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the dev
mailing list