Previously we would sit in the submission routine and spin on the poller and then retry in the event that we could not get CryptoDev to take all of the ops that we had available. The implementation was fine however a recent CryptoDev change requires us to now check the status of attempted submissions instead of assuming that the device was busy. If there was another reason for the failure we don't want to retry or we'll be stuck in an endless retry loop. Changing the current device full handling to match what was done in the compression vbdev makes it easier to handle the new condition and also makes the two vbdevs more consistent with regards to how they manage the DPDK framework API. This patch only changes how we handle full conditions to put the ops on a linked list and resubmit them the next tie the poller runs naturally. A following patch will handle the CryptoDev API change that instigated this change. Signed-off-by: paul luse <paul.e.luse@intel.com> Change-Id: Idcb6e06b6826045f23e59b64eca051f3eee2b850 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/472309 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> |
||
---|---|---|
.. | ||
.gitignore | ||
crypto_ut.c | ||
Makefile |