Linux block layer
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@fb.com>,
	<linux-block@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>
Cc: Bart Van Assche <bart.vanassche@sandisk.com>,
	<linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
	Omar Sandoval <osandov@fb.com>, Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH 0/2] block/SCSI MQ: two RESTART related patches
Date: Tue, 17 Oct 2017 16:47:23 +0100	[thread overview]
Message-ID: <8e604f28-dd20-7818-a25b-985ab537bf70@huawei.com> (raw)
In-Reply-To: <20171017051209.GF15996@ming.t460p>

On 17/10/2017 06:12, Ming Lei wrote:
> On Tue, Oct 17, 2017 at 01:04:16PM +0800, Ming Lei wrote:
>> Hi Jens,
>>
>> The 1st patch runs idle hctx after dealy in scsi_mq_get_budget(),
>> so that we can keep same behaviour with before, and it can be
>> thought as a fix.
>>
>> The 2nd patch cleans up RESTART, and removes handling for TAG_SHARED
>> from current blk-mq's RESTART mechanism because SCSI_MQ can covers its
>> restart by itself, so that no need to handle TAG_SHARED in blk-mq
>> RESTART. And >20% IOPS boost is observed in my rand read test over
>> scsi_debug.
>>
>> John, please test this two patches and see if it may improve your SAS
>> IO performance, and you can find the two patches in the following branch:
>>
>> 	https://github.com/ming1/linux/commits/blk_mq_improve_restart_V1
>

Hi Ming,

As requested, here's my figures for blk_mq_improve_restart_V1:
without default SCSI_MQ, deadline scheduler, CONFIG PREEMPT off
read, rw, write IOPS	
989K, 113K/113K, 835K

with default SCSI_MQ, mq-deadline scheduler, CONFIG PREEMPT off
read, rw, write IOPS	
738K, 130K/130K, 686K

For axboe for-next tip (21ed538):
without default SCSI_MQ, deadline scheduler, CONFIG PREEMPT off
read, rw, write IOPS	
977K, 117K/117K, 821K

with default SCSI_MQ, mq-deadline scheduler, CONFIG PREEMPT off
read, rw, write IOPS	
733K, 128K/128K, 676K

All cases do not have LLDD mq exposed/enabled. So unfortunately not much 
difference with your branch.

cheers,
John

> Forget to mention, you need to either pull the above branch directly
> or apply the two patches against for-next branch of Jens' block
> tree:
>
> 	git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git #for-next
>

  reply	other threads:[~2017-10-17 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17  5:04 [PATCH 0/2] block/SCSI MQ: two RESTART related patches Ming Lei
2017-10-17  5:04 ` [PATCH 1/2] SCSI: run idle hctx after delay in scsi_mq_get_budget() Ming Lei
2017-10-17  5:04 ` [PATCH 2/2] blk-mq: don't handle TAG_SHARED in restart Ming Lei
2017-10-17  5:12 ` [PATCH 0/2] block/SCSI MQ: two RESTART related patches Ming Lei
2017-10-17 15:47   ` John Garry [this message]
2017-10-18  1:30     ` Ming Lei

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=8e604f28-dd20-7818-a25b-985ab537bf70@huawei.com \
    --to=john.garry@huawei.com \
    --cc=axboe@fb.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=ming.lei@redhat.com \
    --cc=osandov@fb.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