Results 1 to 1 of 1

Thread: Kyber as default io scheduler on SSD (Linux 50 series) - A mystery

  1. #1
    Join Date
    Dec 2018
    Beans
    1

    Kyber as default io scheduler on SSD (Linux 50 series) - A mystery

    So I wanted to use kyber (instead of mq-deadline) as default io scheduler for my SSD (Toshiba Q300). What I did is very simple, and it works well. I’ve just created a file /etc/udev/rules.d/60-ioscheduler.rules with the following content:

    Code:
    # set scheduler for NVMe
    ACTION=="add|change", KERNEL=="nvme[0-9]*", ATTR{queue/scheduler}="none"
    # set scheduler for SSD and eMMC
    ACTION=="add|change", KERNEL=="sd[a-z]|mmcblk[0-9]*", ATTR{queue/rotational}=="0", ATTR{queue/scheduler}="kyber"
    # set scheduler for rotating disks
    ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1", ATTR{queue/scheduler}="mq-deadline"
    After rebooting kyber is working as expected:

    Code:
    sandrito@maverick:~$ cat /sys/block/sda/queue/scheduler
    mq-deadline [kyber] none
    So far so good. No need to preload kyber-iosched at boot since I’m using:

    Code:
    ACTION=="add|change"
    But why is it that if I also add kyber-iosched in /etc/modules-load.d/modules.conf my laptop performs much better with lower memory usage and CPU temperature? Isn’t kyber module loaded axactly the same way?
    Last edited by sandrito2; 6 Days Ago at 11:12 PM. Reason: Set default font colour

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •