From: Pavel Machek <pavel@ucw.cz>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: oleksandr@natalenko.name,
Paolo Valente <paolo.valente@linaro.org>,
Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
linux-mtd@lists.infradead.org,
Ulf Hansson <ulf.hansson@linaro.org>,
Richard Weinberger <richard@nod.at>,
Artem Bityutskiy <dedekind1@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>, Jan Kara <jack@suse.cz>,
aherrmann@suse.com, mgorman@suse.com,
Chunyan Zhang <zhang.chunyan@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
bfq-iosched@googlegroups.com, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] block: BFQ default for single queue devices
Date: Fri, 5 Oct 2018 11:49:09 +0200 [thread overview]
Message-ID: <20181005094909.GB17069@amd> (raw)
In-Reply-To: <CACRpkdYG2Y=rspbZ_o=H3REXTEfOcaiqEyQD4kzO=G=d63V3yA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
Hi!
> On another hand, the users of embedded devices, mentioned by Linus,
> > should already know what scheduler to choose because dealing with
> > embedded world assumes the person can decide this on their own, or with
> > the help of abovementioned udev scripts and/or Documentation/ as a
> > reference point.
> >
> > So I see no obstacles here, and the choice to rely on udev by default
> > sounds reasonable.
> >
>
> I am sorry but I do not agree with this.
>
> There are several historical precedents where we have
> concluded that just "have the kernel do the right thing
> by default" is the way to go.
Kernel should do the right thing by default, I agree with Linus W.
Having reasonable defaults is useful; yes, my desktop has udev etc,
but I still want reasonable scheduler when doing fsck in
init=/bin/bash.
Plus, I update kernels more often than distros, and I run various
embedded stuff.
Kernel should just provide reasonable defaults.
And yes, we have "ionice" command and yes, it would be nice if it
worked by default...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-10-05 9:49 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 12:43 [PATCH] block: BFQ default for single queue devices Linus Walleij
2018-10-02 12:43 ` Linus Walleij
2018-10-02 14:31 ` Jens Axboe
2018-10-02 14:31 ` Jens Axboe
2018-10-02 14:45 ` Linus Walleij
2018-10-02 14:45 ` Linus Walleij
2018-10-03 6:29 ` Paolo Valente
2018-10-03 6:29 ` Paolo Valente
2018-10-03 6:53 ` Linus Walleij
2018-10-03 13:25 ` Jan Kara
2018-10-04 7:45 ` Johannes Thumshirn
2018-10-04 7:45 ` Johannes Thumshirn
2018-10-04 8:24 ` Andreas Herrmann
2018-10-03 7:05 ` Artem Bityutskiy
2018-10-03 7:18 ` Linus Walleij
2018-10-03 7:42 ` Damien Le Moal
2018-10-03 7:42 ` Damien Le Moal
2018-10-03 8:28 ` Linus Walleij
2018-10-03 8:53 ` Damien Le Moal
2018-10-03 8:53 ` Damien Le Moal
2018-10-03 8:53 ` Damien Le Moal
2018-10-03 15:53 ` Paolo Valente
2018-10-03 15:53 ` Paolo Valente
2018-10-03 17:34 ` Bryan Gurney
2018-10-04 8:21 ` Linus Walleij
2018-10-04 9:56 ` Ulf Hansson
2018-10-03 12:51 ` Christoph Hellwig
2018-10-03 12:51 ` Christoph Hellwig
2018-10-03 14:58 ` Bart Van Assche
2018-10-03 14:58 ` Bart Van Assche
2018-10-03 15:01 ` Christoph Hellwig
2018-10-03 15:01 ` Christoph Hellwig
2018-10-03 15:15 ` Bart Van Assche
2018-10-03 15:15 ` Bart Van Assche
2018-10-05 6:24 ` Christoph Hellwig
2018-10-05 6:24 ` Christoph Hellwig
2018-10-03 15:52 ` Paolo Valente
2018-10-03 15:52 ` Paolo Valente
2018-10-03 15:52 ` Paolo Valente
2018-10-03 11:49 ` Oleksandr Natalenko
2018-10-03 11:49 ` Oleksandr Natalenko
2018-10-03 14:51 ` Mark Brown
2018-10-03 15:55 ` Paolo Valente
2018-10-03 15:55 ` Paolo Valente
2018-10-03 16:00 ` Bart Van Assche
2018-10-03 16:04 ` Paolo Valente
2018-10-03 16:04 ` Paolo Valente
2018-10-04 7:38 ` Jan Kara
2018-10-04 8:14 ` Linus Walleij
2018-10-04 10:13 ` Mark Brown
2018-10-04 15:10 ` Bart Van Assche
2018-10-04 15:26 ` Mark Brown
2018-10-05 9:49 ` Pavel Machek [this message]
2018-10-04 8:25 ` Linus Walleij
2018-10-03 15:54 ` Bart Van Assche
2018-10-03 15:54 ` Bart Van Assche
2018-10-03 16:02 ` Paolo Valente
2018-10-03 16:02 ` Paolo Valente
2018-10-03 16:09 ` Paolo Valente
2018-10-03 17:22 ` Paolo Valente
2018-10-03 17:22 ` Paolo Valente
2018-10-04 19:25 ` Alan Cox
2018-10-04 19:25 ` Alan Cox
2018-10-04 20:09 ` Bart Van Assche
2018-10-04 20:39 ` Paolo Valente
2018-10-04 20:39 ` Paolo Valente
2018-10-04 22:42 ` Bart Van Assche
2018-10-05 9:16 ` Jan Kara
2018-10-06 3:12 ` Bart Van Assche
2018-10-06 6:46 ` Paolo Valente
2018-10-06 6:46 ` Paolo Valente
2018-10-06 6:46 ` Paolo Valente
2018-10-06 16:20 ` Bart Van Assche
2018-10-06 16:20 ` Bart Van Assche
2018-10-06 16:46 ` Paolo Valente
2018-10-06 16:46 ` Paolo Valente
2018-10-06 16:46 ` Paolo Valente
2018-10-05 9:28 ` Paolo Valente
2018-10-05 9:28 ` Paolo Valente
2018-10-05 6:24 ` Artem Bityutskiy
2018-10-04 20:19 ` Paolo Valente
2018-10-04 20:19 ` Paolo Valente
2018-10-02 21:28 ` Richard Weinberger
2018-10-02 21:28 ` Richard Weinberger
2018-10-03 15:51 ` Paolo Valente
2018-10-03 15:51 ` Paolo Valente
2018-10-03 15:51 ` Paolo Valente
2018-10-05 8:04 ` Pavel Machek
2018-10-05 8:04 ` Pavel Machek
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=20181005094909.GB17069@amd \
--to=pavel@ucw.cz \
--cc=adrian.hunter@intel.com \
--cc=aherrmann@suse.com \
--cc=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=broonie@kernel.org \
--cc=dedekind1@gmail.com \
--cc=jack@suse.cz \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mgorman@suse.com \
--cc=oleksandr@natalenko.name \
--cc=paolo.valente@linaro.org \
--cc=richard@nod.at \
--cc=ulf.hansson@linaro.org \
--cc=zhang.chunyan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.