Linux block layer
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: 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: Mon, 19 Jun 2017 16:52:36 +0800	[thread overview]
Message-ID: <20170619085236.GB20152@yexl-desktop> (raw)
In-Reply-To: <20170619084153.GA14788@lst.de>

On 06/19, Christoph Hellwig wrote:
>On Mon, Jun 19, 2017 at 03:49:43PM +0800, Ye Xiaolong wrote:
>> On 06/19, Christoph Hellwig wrote:
>> >On Mon, Jun 19, 2017 at 02:03:18PM +0800, kernel test robot wrote:
>> >> 
>> >> Greeting,
>> >> 
>> >> FYI, we noticed a -4% regression of fio.write_bw_MBps due to commit:
>> >
>> >What does cat /sys/block/<device>/queue/scheduler say for your test?
>> >Can you try with mq-deadline or bfq and see what the results are?
>> 
>> Could you tell me how to do it? via changing kernel config?
>
>BFQ doesn't seem to be enabled in the config, so it would have to be
>enabled.
>
>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,
Xiaolong

  reply	other threads:[~2017-06-19  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170616082755.22832-1-hch@lst.de>
     [not found] ` <20170619060318.GC23108@yexl-desktop>
2017-06-19  7:09   ` [lkp-robot] [scsi] ebc76736f2: fio.write_bw_MBps -4% regression Christoph Hellwig
2017-06-19  7:49     ` Ye Xiaolong
2017-06-19  8:41       ` Christoph Hellwig
2017-06-19  8:52         ` Ye Xiaolong [this message]
2017-06-19  9:39           ` Christoph Hellwig
2017-06-20  2:16             ` Ye Xiaolong
2017-06-20  6:04               ` Christoph Hellwig

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=20170619085236.GB20152@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkp@01.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