From: Christoph Hellwig <hch@infradead.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-mmc@vger.kernel.org, Ulf Hansson <ulf.hansson@linaro.org>,
linux-block@vger.kernel.org,
Paolo Valente <paolo.valente@linaro.org>
Subject: Re: [PATCH] mmc: core: Imply IOSCHED_BFQ
Date: Tue, 31 Jan 2023 07:11:03 -0800 [thread overview]
Message-ID: <Y9kvh42/T9rdqDH9@infradead.org> (raw)
In-Reply-To: <CACRpkdbd73PEAaNYr2cz=pmw7guHK0-hiPCYXgpgQfy-d9TTTQ@mail.gmail.com>
On Tue, Jan 31, 2023 at 03:05:20PM +0100, Linus Walleij wrote:
> To be clear, "works better" in this context means, solving a problem
> for the interactive user, preventing random freezing of the UI on
> resource-limited (memory, disk throughput) systems under high
> I/O load.
Which already has nothing to do with the mmc driver. And the rest
of your mail makes this even more clear. You want bfq for interactive
systems with little resources and really shitty storage device, which
just happen to use mmc in your use case.
My use case for sd cards OTOH is extremely resource constrained systems
where I absolutely do not want a bloated I/O scheduler. In fact I'd
love to be able to even compile the infrastructure for them away.
In other words: you want distro policy to use bfq for your use case,
but that has no business being in the Kconfig.
next prev parent reply other threads:[~2023-01-31 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 8:47 [PATCH] mmc: core: Imply IOSCHED_BFQ Linus Walleij
2023-01-31 9:01 ` Christoph Hellwig
2023-01-31 9:57 ` Linus Walleij
2023-01-31 13:20 ` Christoph Hellwig
2023-01-31 14:05 ` Linus Walleij
2023-01-31 15:11 ` Christoph Hellwig [this message]
2023-02-01 8:18 ` Linus Walleij
2023-02-01 13:08 ` Christoph Hellwig
2023-02-01 13:19 ` Arnd Bergmann
2023-02-01 14:44 ` Linus Walleij
2023-02-02 15:22 ` Ulf Hansson
2023-02-02 18:04 ` Jens Axboe
2023-02-02 22:14 ` Linus Walleij
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=Y9kvh42/T9rdqDH9@infradead.org \
--to=hch@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=ulf.hansson@linaro.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