![]() ![]() DM's blk-mq support is purely about request-based DM-multipath. You need to use dm_mod.use_blk_mq=Y (not to mention scsi_mod.use_blk_mq=Y)īut that aside, you're hoping to use blk-mq on a bio-based device and that is _never_ going to work. > lrwxrwxrwx 1 root root 8 Apr 30 15:38 /dev/mapper/ss-test ->. > - Maybe a race condition at boot? Let's allocate one manually > lrwxrwxrwx 1 root root 7 Apr 30 06:05 /dev/mapper/ss-fs ->. > - But none of my mapped devices have MQ turned on! (This one is LVM/ext4 > active cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 cpu_list > # cat /sys/class/block/sda/queue/scheduler > - And MQ appears to be properly turned on at the device layer > /sys/module/dm_mod/parameters/use_blk_mq > # cat /sys/module/scsi_mod/parameters/use_blk_mq > scsi_mod.use_blk_mq=1 dm_mod.use_blk_mq=1 > BOOT_IMAGE=/boot/vmlinuz-linux-lts root=/dev/mapper/ss-fs rw > (I have also duplicated this issue on 4.10.11) > Despite all best efforts, I cannot get MQ turned on in the DM layer. Lrwxrwxrwx 1 root root 8 Apr 30 15:38 /dev/mapper/ss-test ->. Maybe a race condition at boot? Let's allocate one manually Lrwxrwxrwx 1 root root 7 Apr 30 06:05 /dev/mapper/ss-fs ->. But none of my mapped devices have MQ turned on! (This one is LVM/ext4 root filesys) # cat /sys/class/block/sda/queue/schedulerĪctive cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 cpu_list dispatched io_poll pending queued run tags And MQ appears to be properly turned on at the device layer # cat /sys/module/scsi_mod/parameters/use_blk_mq /sys/module/dm_mod/parameters/use_blk_mq (I have also duplicated this issue on 4.10.11)īOOT_IMAGE=/boot/vmlinuz-linux-lts root=/dev/mapper/ss-fs rw scsi_mod.use_blk_mq=1 dm_mod.use_blk_mq=1 Despite all best efforts, I cannot get MQ turned on in the DM layer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |