Spdk/test/spdkcli/match_files/spdkcli_pmem.test.match

o- pmemblk .............................................................................................................. [Bdevs: 2]
  o- pmem_bdev0 $(S) [$(UUID), Size=31.6M, Not claimed]
  o- pmem_bdev1 $(S) [$(UUID), Size=31.6M, Not claimed]
test/spdkcli: Add possibility to delete all bdevs for subnodes (aio, error, logical_volume, etc) from bdev node Change-Id: I346437da6cff6b0df6dc8a579da09e77bcddf610 Signed-off-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-on: https://review.gerrithub.io/430074 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> 2018-10-19 18:48:08 +00:00			`o- pmemblk .............................................................................................................. [Bdevs: 2]`
bdev: register bdev's UUID as its alias In many cases, addressing bdevs by their UUIDs is often easier than using their names, which can be somewhat arbitrary. For instance, the NVMe bdev builds a name by addng the n{NSID} suffix to the controller's name, while the UUID is filled with NGUID (if available). The UUID alias is stored in the form defined by RFC 4122, meaning five groups of lower-case hexadecimal characters. It's important to note that bdev layer uses case-sensitive name comparison, so the user needs to use the same textual UUID representation. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: I8b112fb81f29e952459d5f81d97fdc7a591730f8 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/11395 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> 2022-02-03 08:03:15 +00:00			`o- pmem_bdev0 $(S) [$(UUID), Size=31.6M, Not claimed]`
			`o- pmem_bdev1 $(S) [$(UUID), Size=31.6M, Not claimed]`