Skip to content
Snippets Groups Projects
  • Xie Yongji's avatar
    779d82e1
    vduse-blk: Add name option · 779d82e1
    Xie Yongji authored
    
    Currently we use 'id' option as the name of VDUSE device.
    It's a bit confusing since we use one value for two different
    purposes: the ID to identfy the export within QEMU (must be
    distinct from any other exports in the same QEMU process, but
    can overlap with names used by other processes), and the VDUSE
    name to uniquely identify it on the host (must be distinct from
    other VDUSE devices on the same host, but can overlap with other
    export types like NBD in the same process). To make it clear,
    this patch adds a separate 'name' option to specify the VDUSE
    name for the vduse-blk export instead.
    
    Signed-off-by: default avatarXie Yongji <xieyongji@bytedance.com>
    Message-Id: <20220614051532.92-7-xieyongji@bytedance.com>
    Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
    779d82e1
    History
    vduse-blk: Add name option
    Xie Yongji authored
    
    Currently we use 'id' option as the name of VDUSE device.
    It's a bit confusing since we use one value for two different
    purposes: the ID to identfy the export within QEMU (must be
    distinct from any other exports in the same QEMU process, but
    can overlap with names used by other processes), and the VDUSE
    name to uniquely identify it on the host (must be distinct from
    other VDUSE devices on the same host, but can overlap with other
    export types like NBD in the same process). To make it clear,
    this patch adds a separate 'name' option to specify the VDUSE
    name for the vduse-blk export instead.
    
    Signed-off-by: default avatarXie Yongji <xieyongji@bytedance.com>
    Message-Id: <20220614051532.92-7-xieyongji@bytedance.com>
    Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>