From: Bart Van Assche <bvanassche@acm.org>
To: Linus Walleij <linus.walleij@linaro.org>, Jens Axboe <axboe@kernel.dk>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Paolo Valente <paolo.valente@unimore.it>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: move the BFQ io scheduler to orphan state
Date: Thu, 5 Sep 2024 11:18:27 -0700 [thread overview]
Message-ID: <6ea50dbd-06e3-4edf-9bd5-b12b904f94ba@acm.org> (raw)
In-Reply-To: <CACRpkdYr=baNp9n2GDtyw9zH5yzi5psbBWHu9jCitby2rS-fhw@mail.gmail.com>
On 9/5/24 11:05 AM, Linus Walleij wrote:
> For Androids and chromebooks it keeps the device interactive
> during heavy disk (eMMC) activity, such as when Android
> updates a pile of apps (.apk files).
Is that issue perhaps specific to eMMC devices? I have never seen
an Android device with UFS storage becoming unresponsive during app
updates. Additionally, now that the mq-deadline I/O scheduler supports
I/O priorities, it is easy to give foreground I/O a higher priority in
Android than background I/O. All that is needed is to add something like
the following in an .rc file that is executed during boot:
write /dev/blkio/blkio.prio.class promote-to-rt
Bart.
next prev parent reply other threads:[~2024-09-05 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 15:53 [PATCH] MAINTAINERS: move the BFQ io scheduler to orphan state Jens Axboe
2024-09-03 17:20 ` Bart Van Assche
2024-09-03 20:06 ` Bart Van Assche
2024-09-04 13:27 ` Ulf Hansson
2024-09-04 13:47 ` Jens Axboe
2024-09-04 13:59 ` Ulf Hansson
2024-09-04 14:05 ` Jens Axboe
2024-09-05 13:03 ` Linus Walleij
2024-09-05 14:57 ` Jens Axboe
2024-09-05 18:05 ` Linus Walleij
2024-09-05 18:18 ` Bart Van Assche [this message]
2024-09-05 18:34 ` 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=6ea50dbd-06e3-4edf-9bd5-b12b904f94ba@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=paolo.valente@unimore.it \
--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