5c1c946c7a
It seems like DPDK 19.02 has split the "session mempool" into two separate mempools but this isn't really described in the DPDK release notes, so this patch only makes our crypto code behave just like DPDK crypto examples. rte_cryptodev_queue_pair_setup() no longer accepts a separate mempool parameter but instead requires it to be passed through a new field in struct rte_cryptodev_qp_conf, which is also passed as a param to rte_cryptodev_queue_pair_setup(). It's referred to as "session private mempool" instead of "session mempool", which makes some sense since we already use rte_cryptodev_sym_get_private_session_size() (with the word "private" in name) to calculate its size. The other mempool - "session mempool" - now has to be allocated with rte_cryptodev_sym_session_pool_create() instead of regular rte_mempool_create(). Change-Id: I3bc6185855988b864ca59bc1972beaf4f7ea8925 Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/443738 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| crypto_ut.c | ||
| Makefile | ||