4036f95bf8
This at least allows the caller to know there was a problem, and that the messages wasn't actually sent. SPDK by default creates huge rings so this problem should never occur, but out-of-tree use cases may send messages much more often and require at least a notification when it fails. While here, change the thread check to an assert. There's no need to work around someone calling this function with a null thread parameter. Fixes issue #811. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Ie6d432d616be45c7a4232aff1548cef198702bc0 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/472438 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> |
||
|---|---|---|
| .. | ||
| blobfs_async_ut | ||
| blobfs_bdev.c | ||
| blobfs_sync_ut | ||
| tree.c | ||
| Makefile | ||