mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Massimo Burcheri <massimo@burcheri.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	Omar Sandoval <osandov@osandov.com>
Subject: Re: MQ-BFQ crashing on battery mode
Date: Fri, 24 Aug 2018 08:29:16 +0200	[thread overview]
Message-ID: <1535092156.11909.8.camel@burcheri.de> (raw)
In-Reply-To: <a43c5bdd-06ec-ae23-ebd3-bda8c0ea4f5c@kernel.dk>

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

On Wed, 2018-08-22 at 11:42 -0600, Jens Axboe wrote:
> Any chance you can try 4.18 at least?

Of course, I tried the kernel.org sources now, sys-kernel/vanilla-sources-4.18.3 
on Gentoo. The issue is the same.

I wonder that nobody has noticed that issue that I can reproduce on many kernels
since 4.13 or even older. Is it a rare combination with my bcache, luks or
btrfs? Or hardware specific? Or scheduler specific, as even BFQ is not that well
tested on btrfs like the default one.

> Schedulers are specific to the queuing infrastructure, so certain types
> will only be available with MQ and certain types will only be available
> on !MQ.

I noticed that. It's just a bit intransparent from the menuconfig, options don't
mention if a scheduler is working on MQ or not, like CONFIG_IOSCHED_BFQ.
There it's written in the description, while CONFIG_MQ_IOSCHED_KYBER has the
note in the name.
Actually MQ schedulers could depend on BLK_MQ to make it obvious.

Best regards,
Massimo

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-08-24  6:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22  8:20 Massimo Burcheri
2018-08-22  8:30 ` Paolo Valente
2018-08-22 17:42 ` Jens Axboe
2018-08-24  6:29   ` Massimo Burcheri [this message]
2018-08-24  7:12     ` jianchao.wang
2018-08-31  6:49       ` blk-mq " Massimo Burcheri

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=1535092156.11909.8.camel@burcheri.de \
    --to=massimo@burcheri.de \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osandov@osandov.com \
    /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

all inboxes | Powered by JetHome®