+11
−10
Loading
Recently added a new call to bdev modules to inform them of when bdev subsystem init is complete. The intention is for modules like RAID or crypto that need to take some action after the initial bdev subsystem init such as 'build whatever RAID volumes you can, all initial examine callbacks are done' or in the case of crypto 'OK, construct all of your crypto structures for HW and SW PMDs and associate each to configured vbdevs.' Now that I've implemented the crypto case I see that the call was misplaced and will execute following any examine_done call including subsequent bdev registrations. Those cases, for both RAID and crypto, need to follow a different path (examine) since all of the activities associated with the new init_complete() callback are intended just for the very first initialization of SPDK. So, long story short, moving this call so that it's only executed once when subsystem init is done and not on subsequent bdev registrations. Change-Id: I952b90e33fc67d48d86c0a7de2ad47c74a98e839 Signed-off-by:Paul Luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/408209 Tested-by:
SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by:
Ben Walker <benjamin.walker@intel.com> Reviewed-by:
Daniel Verkamp <daniel.verkamp@intel.com>