Block I/O Schedulers: Can they be made selectable/device? @runtime?

Is it still the case that block I/O schedulers (AS, CFQ, etc.)
are only selectable at boot time?

How difficult would it be to allow multiple, concurrent I/O
schedulers running on different block devices?

How close is the kernel to "being there"?  I.e. if someone has a
"regular" hard disk and a high-end solid state disk, can
Linux allow whichever algorithm is best for the hardware?
(or applications if they are run on separate block devices)?

-l




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Block I/O Schedulers: Can they be made selectable/device? @runtime?
    • From: Tejun Heo <[email protected]>
  • Re: Block I/O Schedulers: Can they be made selectable/device? @runtime?
    • From: [email protected]

• Prev by Date: Re: snd-nm256: hard lockup on every second module load after powerup
• Next by Date: Re: swap prefetching merge plans
• Previous by thread: snd-nm256: hard lockup on every second module load after powerup
• Next by thread: Re: Block I/O Schedulers: Can they be made selectable/device? @runtime?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]