[LU-11913] mq-deadline should be in the list of allowed schedulers Created: 01/Feb/19 Updated: 01/Apr/19 Resolved: 27/Feb/19 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.13.0, Lustre 2.10.7, Lustre 2.12.1 |
| Fix Version/s: | Lustre 2.13.0, Lustre 2.12.1 |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Andreas Dilger | Assignee: | Andreas Dilger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | easy | ||
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
The mount.lustre mount process verified that the block device scheduler is using one of the acceptable scheduler types, since using an incorrect scheduler can cause significant performance loss. The currently-allowed schedulers are "noop" and "deadline". With newer kernels, the block multi-queue devices have a new "mq-deadline" scheduler that can also be used, otherwise a message like the following is printed: onyx-32vm7: mount.lustre: change scheduler of /sys/block/vda/queue/scheduler from mq-deadline to deadline This isn't strictly harmful (I don't think it will actually accept "deadline" as a valid scheduler in this case), but it is confusing and should be fixed. |
| Comments |
| Comment by Gerrit Updater [ 01/Feb/19 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/34163 |
| Comment by Gerrit Updater [ 27/Feb/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/34163/ |
| Comment by Peter Jones [ 27/Feb/19 ] |
|
Landed for 2.13 |
| Comment by Gerrit Updater [ 14/Mar/19 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/34426 |
| Comment by Gerrit Updater [ 01/Apr/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/34426/ |