From: Ming Lei <tom.leiming@gmail.com>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Paolo Valente <paolo.valente@linaro.org>,
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: Tue, 8 Aug 2017 19:49:53 +0800 [thread overview]
Message-ID: <CACVXFVMmcU8SWVFsMfRS9co7gZ=0docvm8Y=-HJJG0v9xSRAVw@mail.gmail.com> (raw)
In-Reply-To: <20170808112711.om7z6djl6igsuvnm@techsingularity.net>
On Tue, Aug 8, 2017 at 7:27 PM, Mel Gorman <mgorman@techsingularity.net> wrote:
> On Tue, Aug 08, 2017 at 06:43:03PM +0800, Ming Lei wrote:
>> Hi Mel Gorman,
>>
>> On Tue, Aug 8, 2017 at 6:30 PM, Mel Gorman <mgorman@techsingularity.net> wrote:
>> ....
>> >
>> > o I've queued a subset of tests with Ming's v3 patchset as that was the
>> > latest branch at the time I looked. It'll take quite some time to execute
>> > as the grid I use to collect data is backlogged with other work
>>
>> The latest patchset is in the following post:
>>
>> http://marc.info/?l=linux-block&m=150191624318513&w=2
>>
>> And you can find it in my github:
>>
>> https://github.com/ming1/linux/commits/blk-mq-dispatch_for_scsi.V4
>>
>
> Unfortunately, the tests were queued last Friday and are partially complete
> depending on when machines become available. As it is, v3 will take a few
> days to complete and a requeue would incur further delays. If you believe
> the results will be substantially different then I'll discard v3 and requeue.
Firstly V3 on github(never posted out) causes boot hang if CPU cores is >= 16,
so you need to check if the test is still running, :-(
Also V3 on github may not perform well on IB SRP(or other low latency
SCSI disk), so
I improve bio merge in V4 and make IB SRP's perf better too, and it depends on
devices.
I suggest to focus on V2 posted in mail list(V4 in github).
--
Ming Lei
next prev parent reply other threads:[~2017-08-08 11:49 UTC|newest]
Thread overview: 29+ 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 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 [this message]
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='CACVXFVMmcU8SWVFsMfRS9co7gZ=0docvm8Y=-HJJG0v9xSRAVw@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;
as well as URLs for NNTP newsgroup(s).