From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
linux-kernel@vger.kernel.org, ulf.hansson@linaro.org,
linus.walleij@linaro.org, bfq-iosched@googlegroups.com,
Chris Evich <cevich@redhat.com>,
Patrick Dung <patdung100@gmail.com>,
Thorsten Schubert <tschubert@bafh.org>
Subject: Re: [PATCH BUGFIX] block, bfq: deschedule empty bfq_queues not referred by any process
Date: Wed, 13 Nov 2019 15:25:14 +0100 [thread overview]
Message-ID: <65fc0bffbcb2296d121b3d5a79108e76@natalenko.name> (raw)
In-Reply-To: <2FB3736A-693E-44B9-9D1F-39AE0D016644@linaro.org>
On 13.11.2019 14:52, Paolo Valente wrote:
>> I'm not sure if I see things right, but this commit along with v5.3.11
>> kernel causes almost all boots to hang (for instance, on mounting the
>> FS). Once the scheduler is changed to something else than BFQ (I set
>> the I/O scheduler early via udev rule), multiple reboots go just fine.
>>
>
> If you switch back to bfq after the boot, can you still reproduce the
> hang?
I didn't try to switch schedulers, but what I see now is once the system
is able to boot with BFQ, the I/O can still hang on I/O burst (which for
me happens to happen during VM reboot).
This may also not hang forever, but just slow down considerably. I've
noticed this inside a KVM VM, not on a real HW.
>> Is this commit also applicable to 5.3 kernels?
>
> It is.
OK, thanks for clarification.
--
Oleksandr Natalenko (post-factum)
next prev parent reply other threads:[~2019-11-13 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 7:48 [PATCH BUGFIX] block, bfq: deschedule empty bfq_queues not referred by any process Paolo Valente
2019-11-12 15:23 ` Jens Axboe
2019-11-12 17:49 ` Paolo Valente
2019-11-13 12:57 ` Oleksandr Natalenko
2019-11-13 13:52 ` Paolo Valente
2019-11-13 14:25 ` Oleksandr Natalenko [this message]
2019-11-13 15:01 ` Oleksandr Natalenko
2019-11-13 17:42 ` Paolo Valente
2019-11-13 22:46 ` Jens Axboe
2019-11-14 9:22 ` Paolo Valente
2019-11-14 8:53 ` Oleksandr Natalenko
2019-11-14 9:23 ` Paolo Valente
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=65fc0bffbcb2296d121b3d5a79108e76@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=cevich@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=patdung100@gmail.com \
--cc=tschubert@bafh.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