From: Mel Gorman <mgorman@techsingularity.net>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Ming Lei <tom.leiming@gmail.com>,
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>
Subject: Re: Switching to MQ by default may generate some bug reports
Date: Thu, 3 Aug 2017 11:46:57 +0100 [thread overview]
Message-ID: <20170803104657.eyxuona33ar5cpp4@techsingularity.net> (raw)
In-Reply-To: <DAC70C00-B51D-4752-8EA7-EA55368918EC@linaro.org>
On Thu, Aug 03, 2017 at 11:44:06AM +0200, Paolo Valente wrote:
> > That series is dealing with problems with legacy-deadline vs mq-none where
> > as the bulk of the problems reported in this mail are related to
> > legacy-CFQ vs mq-BFQ.
> >
>
> Out-of-curiosity: you get no regression with mq-none or mq-deadline?
>
I didn't test mq-none as the underlying storage was not fast enough to
make a legacy-noop vs mq-none meaningful. legacy-deadline vs mq-deadline
did show small regressions on some workloads but not as dramatic and
small enough that it would go unmissed in some cases.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2017-08-03 10:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 8:51 Switching to MQ by default may generate some bug reports Mel Gorman
2017-08-03 9:17 ` Ming Lei
2017-08-03 9:32 ` Ming Lei
2017-08-03 9:42 ` Mel Gorman
2017-08-03 9:44 ` Paolo Valente
2017-08-03 9:44 ` Paolo Valente
2017-08-03 10:46 ` Mel Gorman [this message]
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 9:21 ` Paolo Valente
2017-08-03 11:01 ` Mel Gorman
2017-08-04 7:26 ` Paolo Valente
2017-08-04 7:26 ` Paolo Valente
2017-08-04 11:01 ` Mel Gorman
2017-08-04 22:05 ` Paolo Valente
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:35 ` Paolo Valente
2017-08-07 17:32 ` Paolo Valente
2017-08-07 17:32 ` Paolo Valente
2017-08-07 18:42 ` Paolo Valente
2017-08-07 18:42 ` Paolo Valente
2017-08-08 8:06 ` Paolo Valente
2017-08-08 8:06 ` Paolo Valente
2017-08-08 17:33 ` 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-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
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=20170803104657.eyxuona33ar5cpp4@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=tom.leiming@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.