From: Jens Axboe <axboe@kernel.dk>
To: Khazhismel Kumykov <khazhy@chromium.org>
Cc: linux-block@vger.kernel.org,
Khazhismel Kumykov <khazhy@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block: allow specifying default iosched in config
Date: Tue, 4 Oct 2022 14:22:21 -0600 [thread overview]
Message-ID: <736d9e73-8f19-cc21-375e-140e4ab61383@kernel.dk> (raw)
In-Reply-To: <166490172029.91699.2910906888136711371.b4-ty@kernel.dk>
On 10/4/22 10:42 AM, Jens Axboe wrote:
> On Mon, 26 Sep 2022 15:01:34 -0700, Khazhismel Kumykov wrote:
>> Setting IO scheduler at device init time in kernel is useful, and moving
>> this option into kernel config makes it possible to build different
>> kernels with different default schedulers from the same tree.
>>
>> Order deadline->none->rest to retain current behavior of using "none" by
>> default if mq-deadline is not enabled.
>>
>> [...]
>
> Applied, thanks!
>
> [1/1] block: allow specifying default iosched in config
> commit: ad9d3da2d07e0b2966e3ced843a0e2229410e26a
I'm going to drop this one for now since we still have
active discussion on it and it's very late (actually too late)
to be debating 6.1.
--
Jens Axboe
prev parent reply other threads:[~2022-10-04 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 22:01 [PATCH] block: allow specifying default iosched in config Khazhismel Kumykov
2022-09-26 22:16 ` Chaitanya Kulkarni
2022-10-03 23:02 ` Khazhy Kumykov
2022-10-04 6:12 ` Damien Le Moal
2022-10-04 18:33 ` Khazhy Kumykov
2022-10-04 22:40 ` Damien Le Moal
2022-10-04 23:15 ` Khazhy Kumykov
2022-10-10 7:20 ` Christoph Hellwig
2022-10-17 17:22 ` Khazhy Kumykov
2022-10-18 8:27 ` Christoph Hellwig
2022-10-04 16:42 ` Jens Axboe
2022-10-04 20:22 ` Jens Axboe [this message]
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=736d9e73-8f19-cc21-375e-140e4ab61383@kernel.dk \
--to=axboe@kernel.dk \
--cc=khazhy@chromium.org \
--cc=khazhy@google.com \
--cc=linux-block@vger.kernel.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