Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1723392 > unrolled thread
| Started by | Jens Axboe <axboe@kernel.dk> |
|---|---|
| First post | 2017-08-30 16:30 +0200 |
| Last post | 2017-08-30 16:30 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RFC] block: deprecate choosing elevator via boot param Jens Axboe <axboe@kernel.dk> - 2017-08-30 16:30 +0200
| From | Jens Axboe <axboe@kernel.dk> |
|---|---|
| Date | 2017-08-30 16:30 +0200 |
| Subject | Re: [RFC] block: deprecate choosing elevator via boot param |
| Message-ID | <ukcaf-ZN-39@gated-at.bofh.it> |
On 08/14/2017 03:27 AM, Oleksandr Natalenko wrote: > Setting I/O scheduler via kernel command line is not flexible enough > anymore. Different schedulers might be desirable for different types > of devices (SSDs and HDDs, for instance). Moreover, setting elevator > while using blk-mq framework does not work in this way already. > > This commit enables warning if user specifies "elevator" boot param. > Removing this option at all might be considered in some future. Not a huge fan of doing it like this, it'll just add a bunch of noise to the dmesg output that people will ignore. It doesn't bring us closer to being able to remove the option. I think we should just let it die over time. This will happen naturally since the blk-mq scheduling framework does not support it. Once we have everything converted, the option will end up doing nothing. Then we can eventually kill it. -- Jens Axboe
Back to top | Article view | linux.kernel
csiph-web