4368937b4e
spdk_bdev_part_construct() must be now called on the same thread that called spdk_bdev_part_base_construct(). This was always the case so far and I don't see any other case where thread safety could be useful, so just remove it. The doxygen doesn't say anything about it either. Even in GPT case, we create a base directly as a part of examine and then create part bdevs in the spdk_bdev_read() completion callback, but that callback will be always executed on the same thread which issued the read. Change-Id: I752f2a7f08c9faf4231ed53a46b700b33fa13697 Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/466024 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> |
||
|---|---|---|
| .. | ||
| bdev_rpc.c | ||
| bdev.c | ||
| Makefile | ||
| part.c | ||
| scsi_nvme.c | ||
| vtune.c | ||