From: Christoph Hellwig <hch@lst.de>
To: Ye Xiaolong <xiaolong.ye@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org, lkp@01.org,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: [lkp-robot] [scsi] ebc76736f2: fio.write_bw_MBps -4% regression
Date: Tue, 20 Jun 2017 08:04:28 +0200 [thread overview]
Message-ID: <20170620060428.GA7051@lst.de> (raw)
In-Reply-To: <20170620021636.GH14764@yexl-desktop>
On Tue, Jun 20, 2017 at 10:16:36AM +0800, Ye Xiaolong wrote:
> Hi, Christoph
>
> On 06/19, Christoph Hellwig wrote:
> >On Mon, Jun 19, 2017 at 04:52:36PM +0800, Ye Xiaolong wrote:
> >> >I've not seen a compile-time option for the MQ I/O scheduler (unlike
> >> >the legacy one), so the way to change it would be to echo the name to
> >> >/sys/block/<device>/queue/scheduler
> >>
> >> echo mq-deadline > /sys/block/<device>/queue/scheduler ?
> >>
> >> I'll try and post the results once I get it.
> >
> >Thanks!
>
> I've re-run the test and cat /sys/block/sda/queue/scheduler and
> /sys/block/sda/queue/scheduler, and both showed "[mq-deadline] kyber none",
> Does it mean they have already set as 'mq-deadline'?
Yes, it seems like you're already using mq-deadline, but bfq isn't even
available.
next prev parent reply other threads:[~2017-06-20 6:04 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 [this message]
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
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=20170620060428.GA7051@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@01.org \
--cc=xiaolong.ye@intel.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).