mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ming Lei <tom.leiming@gmail.com>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jens Axboe <axboe@kernel.dk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-block <linux-block@vger.kernel.org>,
	Paolo Valente <paolo.valente@linaro.org>
Subject: Re: Switching to MQ by default may generate some bug reports
Date: Thu, 3 Aug 2017 17:17:21 +0800	[thread overview]
Message-ID: <CACVXFVP3M64ebQQM-aaBs8-TKFqkgVCvO2TQbB6xLcp9_5Q3Sg@mail.gmail.com> (raw)
In-Reply-To: <20170803085115.r2jfz2lofy5spfdb@techsingularity.net>

Hi Mel Gorman,

On Thu, Aug 3, 2017 at 4:51 PM, Mel Gorman <mgorman@techsingularity.net> wrote:
> Hi Christoph,
>
> I know the reasons for switching to MQ by default but just be aware that it's
> not without hazards albeit it the biggest issues I've seen are switching
> CFQ to BFQ. On my home grid, there is some experimental automatic testing
> running every few weeks searching for regressions. Yesterday, it noticed
> that creating some work files for a postgres simulator called pgioperf
> was 38.33% slower and it auto-bisected to the switch to MQ. This is just
> linearly writing two files for testing on another benchmark and is not
> remarkable. The relevant part of the report is

We saw some SCSI-MQ performance issue too, please see if the following
patchset fixes your issue:

http://marc.info/?l=linux-block&m=150151989915776&w=2

Thanks,
Ming

  reply	other threads:[~2017-08-03  9:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03  8:51 Mel Gorman
2017-08-03  9:17 ` Ming Lei [this message]
2017-08-03  9:32   ` Ming Lei
2017-08-03  9:42   ` Mel Gorman
2017-08-03  9:44     ` Paolo Valente
2017-08-03 10:46       ` Mel Gorman
2017-08-03  9:57     ` Ming Lei
2017-08-03 10:47       ` Mel Gorman
2017-08-03 11:48         ` Ming Lei
2017-08-03  9:21 ` Paolo Valente
2017-08-03 11:01   ` Mel Gorman
2017-08-04  7:26     ` Paolo Valente
2017-08-04 11:01       ` Mel Gorman
2017-08-04 22:05         ` Paolo Valente
2017-08-05 11:54           ` Mel Gorman
2017-08-07 17:35             ` Paolo Valente
2017-08-07 17:32           ` Paolo Valente
2017-08-07 18:42             ` Paolo Valente
2017-08-08  8:06               ` Paolo Valente
2017-08-08 17:33                 ` Paolo Valente
2017-08-08 18:27                   ` Mel Gorman
2017-08-09 21:49                   ` Paolo Valente
2017-08-10  8:44                     ` Mel Gorman
2017-08-08 10:30             ` Mel Gorman
2017-08-08 10:43               ` Ming Lei
2017-08-08 11:27                 ` Mel Gorman
2017-08-08 11:49                   ` Ming Lei
2017-08-08 11:55                     ` Mel Gorman
2017-08-08 17:16               ` 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=CACVXFVP3M64ebQQM-aaBs8-TKFqkgVCvO2TQbB6xLcp9_5Q3Sg@mail.gmail.com \
    --to=tom.leiming@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --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
all inboxes | Powered by JetHome®