From: Linda Walsh <lkml@tlinx.org>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Block I/O Schedulers: Can they be made selectable/device? @runtime?
Date: Sat, 25 Mar 2006 22:41:00 -0800 [thread overview]
Message-ID: <4426377C.7000605@tlinx.org> (raw)
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
next reply other threads:[~2006-03-26 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 6:41 Linda Walsh [this message]
2006-03-26 7:06 ` Block I/O Schedulers: Can they be made selectable/device? @runtime? Valdis.Kletnieks
2006-03-27 3:20 ` Linda Walsh
2006-03-27 6:19 ` Randy.Dunlap
2006-03-27 8:40 ` [PATCH] 2.6.16 Block I/O Schedulers - document runtime selection Valdis.Kletnieks
2006-03-29 4:10 ` Block I/O Schedulers: Can they be made selectable/device? @runtime? Tejun Heo
2006-03-29 7:21 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4426377C.7000605@tlinx.org \
--to=lkml@tlinx.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox