"bluestore_ioring" has the hint that it only affect bluestore when
it uses KernelDevice/HMSMRDevice driver. However, it also affects
librbd when librbd use blk driver and "bluestore_ioring" is configured
in global section.
Refine the name to avoid this hint.
Suggested-by: Kefu Chai <kefu@redhat.com>
Signed-off-by: Changcheng Liu <changcheng.liu@aliyun.com>
fd_directs.resize(WRITE_LIFE_MAX, -1);
fd_buffereds.resize(WRITE_LIFE_MAX, -1);
- bool use_ioring = cct->_conf.get_val<bool>("bluestore_ioring");
+ bool use_ioring = cct->_conf.get_val<bool>("bdev_ioring");
unsigned int iodepth = cct->_conf->bdev_aio_max_queue_depth;
if (use_ioring && ioring_queue_t::supported()) {
fd_directs.resize(WRITE_LIFE_MAX, -1);
fd_buffereds.resize(WRITE_LIFE_MAX, -1);
- bool use_ioring = cct->_conf.get_val<bool>("bluestore_ioring");
+ bool use_ioring = cct->_conf.get_val<bool>("bdev_ioring");
unsigned int iodepth = cct->_conf->bdev_aio_max_queue_depth;
if (use_ioring && ioring_queue_t::supported()) {
.set_default(0)
.set_description("Space reserved at DB device and not allowed for 'use some extra' policy usage. Overrides 'bluestore_volume_selection_reserved_factor' setting and introduces straightforward limit."),
- Option("bluestore_ioring", Option::TYPE_BOOL, Option::LEVEL_ADVANCED)
+ Option("bdev_ioring", Option::TYPE_BOOL, Option::LEVEL_ADVANCED)
.set_default(false)
.set_description("Enables Linux io_uring API instead of libaio"),