From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "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: Wed, 12 Jul 2017 14:18:14 +0000 [thread overview]
Message-ID: <1499869093.8204.2.camel@wdc.com> (raw)
In-Reply-To: <581a258d-3da8-5b01-f528-0ce11b74b65e@huawei.com>
On Wed, 2017-07-12 at 09:26 +0100, John Garry wrote:
> > > What block driver controls the block device for which the performance
> > > regression
> > > has been observed? How many hardware queues were created by that block
> > > driver
> > > (see also /sys/block/*/mq/...)?
>
> Just confirming that we have only 1 queue:
> /sys/block/sdc/mq/0 as example
Hello John,
Can you also check the I/O scheduler that has been selected?
Thanks,
Bart.
next prev parent reply other threads:[~2017-07-12 14:18 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 [this message]
2017-07-12 15:54 ` Jonathan Cameron
2017-07-14 9:56 ` Jonathan Cameron
2017-07-14 12:45 ` hch
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=1499869093.8204.2.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=hch@lst.de \
--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).