From: "hch@lst.de" <hch@lst.de>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Bart Van Assche <Bart.VanAssche@wdc.com>,
"hch@lst.de" <hch@lst.de>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"john.garry@huawei.com" <john.garry@huawei.com>,
"linuxarm@huawei.com" <linuxarm@huawei.com>
Subject: Re: [PATCH] scsi: default to scsi-mq
Date: Fri, 14 Jul 2017 14:45:39 +0200 [thread overview]
Message-ID: <20170714124539.GA26686@lst.de> (raw)
In-Reply-To: <20170714175641.00001cb0@huawei.com>
On Fri, Jul 14, 2017 at 05:56:41PM +0800, Jonathan Cameron wrote:
> Just wondering if you had any thoughts on how we can proceed with tracking
> down this regression?
>
> I'm not familiar enough with the multiqueue code to really know where
> to start.
>
> If there are any other tests that would be of use, let us know.
Can you send the blktrace and perf output for each of the runs?
Thanks!
next prev parent reply other threads:[~2017-07-14 12:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 8:27 [PATCH] scsi: default to scsi-mq Christoph Hellwig
2017-06-19 6:03 ` [lkp-robot] [scsi] ebc76736f2: fio.write_bw_MBps -4% regression kernel test robot
2017-06-19 7:09 ` Christoph Hellwig
2017-06-19 7:49 ` Ye Xiaolong
2017-06-19 8:41 ` Christoph Hellwig
2017-06-19 8:52 ` Ye Xiaolong
2017-06-19 9:39 ` Christoph Hellwig
2017-06-20 2:16 ` Ye Xiaolong
2017-06-20 6:04 ` Christoph Hellwig
2017-06-22 15:05 ` [PATCH] scsi: default to scsi-mq Martin Wilck
2017-06-26 9:48 ` Christoph Hellwig
2017-06-26 12:13 ` Bart Van Assche
2017-06-26 15:31 ` Bart Van Assche
2017-06-26 18:55 ` Martin Wilck
2017-06-27 6:07 ` Bart Van Assche
2017-07-10 15:50 ` Bart Van Assche
2017-07-11 10:22 ` John Garry
2017-07-11 13:32 ` Bart Van Assche
2017-07-11 14:14 ` John Garry
2017-07-11 15:46 ` Bart Van Assche
2017-07-11 17:34 ` John Garry
2017-07-12 8:26 ` John Garry
2017-07-12 14:18 ` Bart Van Assche
2017-07-12 15:54 ` Jonathan Cameron
2017-07-14 9:56 ` Jonathan Cameron
2017-07-14 12:45 ` hch [this message]
2017-07-18 15:58 ` Jonathan Cameron
2017-07-18 16:24 ` Jonathan Cameron
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=20170714124539.GA26686@lst.de \
--to=hch@lst.de \
--cc=Bart.VanAssche@wdc.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=john.garry@huawei.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.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;
as well as URLs for NNTP newsgroup(s).