From: Takashi Iwai <tiwai@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Paolo Valente <paolo.valente@linaro.org>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] bfq probe failed on 4.19-rc3
Date: Tue, 11 Sep 2018 18:16:38 +0200 [thread overview]
Message-ID: <s5hy3c8j9g9.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5h7ejsnhds.wl-tiwai@suse.de>
On Tue, 11 Sep 2018 18:11:43 +0200,
Takashi Iwai wrote:
>
> On Tue, 11 Sep 2018 18:09:44 +0200,
> Jens Axboe wrote:
> >
> > On 9/11/18 10:03 AM, Takashi Iwai wrote:
> > > Hi,
> > >
> > > I noticed that bfq doesn't appear in the I/O scheduler list on
> > > 4.19-rc3. It seems that blkcg_policy_register() at the beginning of
> > > bfq_init() returns -ENOSPC, hence the probe aborts silently.
> > >
> > > Is this already addressed?
> >
> > Haven't heard about this one before. What kernel did you last use that
> > worked?
>
> IIRC, 4.18 worked fine. Let me see whether I have a backup...
Confirmed that 4.18 worked. It's also with CONFIG_IOSCHED_BFQ=y and
CONFIG_BFQ_GROUP_IOSCHED=y.
And, 4.19-rc3 with CONFIG_BFQ_GROUP_IOSCHED=n seems working, too (as
expected from the error above).
(BTW I'll have to leave from this machine now. For any further
inquiry, I'll check tomorrow, sorry.)
Takashi
next prev parent reply other threads:[~2018-09-11 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 16:03 [REGRESSION] bfq probe failed on 4.19-rc3 Takashi Iwai
2018-09-11 16:09 ` Jens Axboe
2018-09-11 16:11 ` Takashi Iwai
2018-09-11 16:16 ` Takashi Iwai [this message]
2018-09-11 16:20 ` Jens Axboe
2018-09-11 16:48 ` Jeff Moyer
2018-09-11 16:49 ` Jens Axboe
2018-09-11 16:51 ` Jeff Moyer
2018-09-11 16:54 ` Jens Axboe
2018-09-11 16:57 ` Jeff Moyer
2018-09-11 16:59 ` Jens Axboe
2018-09-12 8:58 ` Takashi Iwai
2018-09-12 14:31 ` 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=s5hy3c8j9g9.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@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