module/blob_bdev: add possibility to change size of bs_dev

spdk bdevs can change their size in run time,
so far there was no way for bs_dev to change its size too
without re-creating it.

Blobstore

module/blob_bdev: add possibility to change size of bs_dev

spdk bdevs can change their size in run time,
so far there was no way for bs_dev to change its size too
without re-creating it.

Blobstore size in general is determined from size written down
in super block. Size of bs_dev is used in following cases:
- initializing blobstore (therefore will become super->size)
- loading blobstore (to check if super->size is not larger)
- growing blobstore (combines two of the above)
- parsing/writing out super block when super->size is 0

Last one is for compatibility with old versions of blobstore.

This effectively means bs_dev size is not used in run-time,
changing it will not affect blobstore even after reloads.
Either way re-creating bs_dev already changed its size.

This patch proposes adding interface that will allow to change
the bs_dev size in run-time, and later in the series add
a way to grow blobstore without reloading it.

There is no need to add a way to revert the bs_dev size.
All error handling for changes in super->size is done in
blobstore.

Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Change-Id: I3d7872d91f3b24d40976b4a8c64df860ddf642ae
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/19453
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <jim.harris@samsung.com>
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>

show more ...

remove spdk_bdev_create_bs_dev_from_desc from map file

Commit 3e15b356f3fd removed spdk_bdev_create_bs_dev_from_desc but missed
removing it from the map file.

Signed-off-by: Mike Gerdts <mgerdts@nv

remove spdk_bdev_create_bs_dev_from_desc from map file

Commit 3e15b356f3fd removed spdk_bdev_create_bs_dev_from_desc but missed
removing it from the map file.

Signed-off-by: Mike Gerdts <mgerdts@nvidia.com>
Change-Id: I0e0932e787b688753478a08f3b5b79e441ba30e7
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14584
Community-CI: Mellanox Build Bot
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>

show more ...

blob/bdev: Add an API spdk_bdev_create_bs_dev_ext()

spdk_bdev_open_ext() requires the caller to use bdev_event_cb_t
and bdev_event_cb_t is more extensible than bdev_remove_cb_t.
Hence use bdev_event

blob/bdev: Add an API spdk_bdev_create_bs_dev_ext()

spdk_bdev_open_ext() requires the caller to use bdev_event_cb_t
and bdev_event_cb_t is more extensible than bdev_remove_cb_t.
Hence use bdev_event_t as an argument.

spdk_bdev_open_ext() calls spdk_bdev_get_by_name() inside and
spdk_bdev_create_bs_dev_ext() calls spdk_bdev_open_ext() inside.
The caller needs to know if the spdk_bdev_get_by_name() succeeded.
Hence spdk_bdev_create_bs_dev_ext() returns return code by return
value and returns the created bs_dev by double pointer.

Signed-off-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Change-Id: I1c225bfb66db036439c69c459f39c86684d8a540
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4692
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>

show more ...

module/blob_bdev: add a map file.

Signed-off-by: Seth Howell <seth.howell@intel.com>
Change-Id: Ibc4ccc29fc254e26685d9d0fb2e004f73cd3c0cd
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/234

module/blob_bdev: add a map file.

Signed-off-by: Seth Howell <seth.howell@intel.com>
Change-Id: Ibc4ccc29fc254e26685d9d0fb2e004f73cd3c0cd
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2342
Community-CI: Mellanox Build Bot
Community-CI: Broadcom CI
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>

show more ...