All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "ming.lei@redhat.com" <ming.lei@redhat.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"hch@infradead.org" <hch@infradead.org>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	"snitzer@redhat.com" <snitzer@redhat.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"axboe@fb.com" <axboe@fb.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
	"loberman@redhat.com" <loberman@redhat.com>,
	"dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: [PATCH 1/5] block: don't call blk_mq_delay_run_hw_queue() in case of BLK_STS_RESOURCE
Date: Mon, 18 Sep 2017 15:18:16 +0000	[thread overview]
Message-ID: <1505747894.2685.6.camel@wdc.com> (raw)
In-Reply-To: <20170917124000.GB6289@ming.t460p>

On Sun, 2017-09-17 at 20:40 +0800, Ming Lei wrote:
> "if no request has completed before the delay has expired" can't be a
> reason to rerun the queue, because the queue can still be busy.

That statement of you shows that there are important aspects of the SCSI
core and dm-mpath driver that you don't understand.

> I suggest to understand the root cause, instead of keeping this
> ugly random delay because run hw queue after 100ms may be useless
> in 99.99% times.

If you are still looking at removing the blk_mq_delay_run_hw_queue() calls
then I think you are looking in the wrong direction. What kind of problem
are you trying to solve? Is it perhaps that there can be a delay between
dm-mpath request completion and the queueing of a new request? If so,
adding a queue run call into the dm-mpath end_io callback is probably
sufficient and probably can replace this entire patch series.

Bart.

WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "ming.lei@redhat.com" <ming.lei@redhat.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"hch@infradead.org" <hch@infradead.org>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	"snitzer@redhat.com" <snitzer@redhat.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"axboe@fb.com" <axboe@fb.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
	"loberman@redhat.com" <loberman@redhat.com>,
	"dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: [PATCH 1/5] block: don't call blk_mq_delay_run_hw_queue() in case of BLK_STS_RESOURCE
Date: Mon, 18 Sep 2017 15:18:16 +0000	[thread overview]
Message-ID: <1505747894.2685.6.camel@wdc.com> (raw)
In-Reply-To: <20170917124000.GB6289@ming.t460p>

T24gU3VuLCAyMDE3LTA5LTE3IGF0IDIwOjQwICswODAwLCBNaW5nIExlaSB3cm90ZToNCj4gImlm
IG5vIHJlcXVlc3QgaGFzIGNvbXBsZXRlZCBiZWZvcmUgdGhlIGRlbGF5IGhhcyBleHBpcmVkIiBj
YW4ndCBiZSBhDQo+IHJlYXNvbiB0byByZXJ1biB0aGUgcXVldWUsIGJlY2F1c2UgdGhlIHF1ZXVl
IGNhbiBzdGlsbCBiZSBidXN5Lg0KDQpUaGF0IHN0YXRlbWVudCBvZiB5b3Ugc2hvd3MgdGhhdCB0
aGVyZSBhcmUgaW1wb3J0YW50IGFzcGVjdHMgb2YgdGhlIFNDU0kNCmNvcmUgYW5kIGRtLW1wYXRo
IGRyaXZlciB0aGF0IHlvdSBkb24ndCB1bmRlcnN0YW5kLg0KDQo+IEkgc3VnZ2VzdCB0byB1bmRl
cnN0YW5kIHRoZSByb290IGNhdXNlLCBpbnN0ZWFkIG9mIGtlZXBpbmcgdGhpcw0KPiB1Z2x5IHJh
bmRvbSBkZWxheSBiZWNhdXNlIHJ1biBodyBxdWV1ZSBhZnRlciAxMDBtcyBtYXkgYmUgdXNlbGVz
cw0KPiBpbiA5OS45OSUgdGltZXMuDQoNCklmIHlvdSBhcmUgc3RpbGwgbG9va2luZyBhdCByZW1v
dmluZyB0aGUgYmxrX21xX2RlbGF5X3J1bl9od19xdWV1ZSgpIGNhbGxzDQp0aGVuIEkgdGhpbmsg
eW91IGFyZSBsb29raW5nIGluIHRoZSB3cm9uZyBkaXJlY3Rpb24uIFdoYXQga2luZCBvZiBwcm9i
bGVtDQphcmUgeW91IHRyeWluZyB0byBzb2x2ZT8gSXMgaXQgcGVyaGFwcyB0aGF0IHRoZXJlIGNh
biBiZSBhIGRlbGF5IGJldHdlZW4NCmRtLW1wYXRoIHJlcXVlc3QgY29tcGxldGlvbiBhbmQgdGhl
IHF1ZXVlaW5nIG9mIGEgbmV3IHJlcXVlc3Q/IElmIHNvLA0KYWRkaW5nIGEgcXVldWUgcnVuIGNh
bGwgaW50byB0aGUgZG0tbXBhdGggZW5kX2lvIGNhbGxiYWNrIGlzIHByb2JhYmx5DQpzdWZmaWNp
ZW50IGFuZCBwcm9iYWJseSBjYW4gcmVwbGFjZSB0aGlzIGVudGlyZSBwYXRjaCBzZXJpZXMuDQoN
CkJhcnQu

WARNING: multiple messages have this Message-ID (diff)
From: Bart.VanAssche@wdc.com (Bart Van Assche)
Subject: [PATCH 1/5] block: don't call blk_mq_delay_run_hw_queue() in case of BLK_STS_RESOURCE
Date: Mon, 18 Sep 2017 15:18:16 +0000	[thread overview]
Message-ID: <1505747894.2685.6.camel@wdc.com> (raw)
In-Reply-To: <20170917124000.GB6289@ming.t460p>

On Sun, 2017-09-17@20:40 +0800, Ming Lei wrote:
> "if no request has completed before the delay has expired" can't be a
> reason to rerun the queue, because the queue can still be busy.

That statement of you shows that there are important aspects of the SCSI
core and dm-mpath driver that you don't understand.

> I suggest to understand the root cause, instead of keeping this
> ugly random delay because run hw queue after 100ms may be useless
> in 99.99% times.

If you are still looking at removing the blk_mq_delay_run_hw_queue() calls
then I think you are looking in the wrong direction. What kind of problem
are you trying to solve? Is it perhaps that there can be a delay between
dm-mpath request completion and the queueing of a new request? If so,
adding a queue run call into the dm-mpath end_io callback is probably
sufficient and probably can replace this entire patch series.

Bart.

  reply	other threads:[~2017-09-18 15:18 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15 16:44 [PATCH 0/5] dm-mpath: improve I/O schedule Ming Lei
2017-09-15 16:44 ` Ming Lei
2017-09-15 16:44 ` [PATCH 1/5] block: don't call blk_mq_delay_run_hw_queue() in case of BLK_STS_RESOURCE Ming Lei
2017-09-15 16:44   ` Ming Lei
2017-09-15 17:57   ` Bart Van Assche
2017-09-15 17:57     ` Bart Van Assche
2017-09-15 17:57     ` Bart Van Assche
2017-09-17 12:40     ` Ming Lei
2017-09-17 12:40       ` Ming Lei
2017-09-18 15:18       ` Bart Van Assche [this message]
2017-09-18 15:18         ` Bart Van Assche
2017-09-18 15:18         ` Bart Van Assche
2017-09-19  5:43         ` Ming Lei
2017-09-19  5:43           ` Ming Lei
2017-09-19 15:36           ` Bart Van Assche
2017-09-19 15:36             ` Bart Van Assche
2017-09-19 15:36             ` Bart Van Assche
2017-09-19 15:56             ` Mike Snitzer
2017-09-19 15:56               ` Mike Snitzer
2017-09-19 16:04               ` Ming Lei
2017-09-19 16:04                 ` Ming Lei
2017-09-19 16:49                 ` Bart Van Assche
2017-09-19 16:49                   ` Bart Van Assche
2017-09-19 16:49                   ` Bart Van Assche
2017-09-19 16:55                   ` Ming Lei
2017-09-19 16:55                     ` Ming Lei
2017-09-19 18:42                     ` Bart Van Assche
2017-09-19 18:42                       ` Bart Van Assche
2017-09-19 18:42                       ` Bart Van Assche
2017-09-19 22:44                       ` Ming Lei
2017-09-19 22:44                         ` Ming Lei
2017-09-19 23:25                         ` Bart Van Assche
2017-09-19 23:25                           ` Bart Van Assche
2017-09-19 23:25                           ` Bart Van Assche
2017-09-19 23:50                           ` Mike Snitzer
2017-09-19 23:50                             ` Mike Snitzer
2017-09-20  1:13                             ` Ming Lei
2017-09-20  1:13                               ` Ming Lei
2017-09-20  1:19                   ` Ming Lei
2017-09-20  1:19                     ` Ming Lei
2017-09-19 15:48           ` Mike Snitzer
2017-09-19 15:48             ` Mike Snitzer
2017-09-19 15:52             ` Bart Van Assche
2017-09-19 15:52               ` Bart Van Assche
2017-09-19 15:52               ` Bart Van Assche
2017-09-19 16:03               ` Mike Snitzer
2017-09-19 16:03                 ` Mike Snitzer
2017-09-19 16:07             ` Ming Lei
2017-09-19 16:07               ` Ming Lei
2017-09-15 16:44 ` [PATCH 2/5] dm-mpath: return DM_MAPIO_REQUEUE in case of rq allocation failure Ming Lei
2017-09-15 17:29   ` Bart Van Assche
2017-09-15 17:29     ` Bart Van Assche
2017-09-15 20:06     ` Mike Snitzer
2017-09-15 20:48       ` Bart Van Assche
2017-09-15 20:48         ` Bart Van Assche
2017-09-17 13:23       ` Ming Lei
2017-09-19 14:41         ` Mike Snitzer
2017-09-19 15:56           ` Ming Lei
2017-09-17 12:51     ` Ming Lei
2017-09-15 16:44 ` [PATCH 3/5] dm-mpath: remove annoying message of 'blk_get_request() returned -11' Ming Lei
2017-09-15 16:44 ` [PATCH 4/5] block: export blk_update_nr_requests Ming Lei
2017-09-15 16:44 ` [PATCH 5/5] dm-mpath: improve I/O schedule Ming Lei
2017-09-15 20:10   ` Mike Snitzer
2017-09-15 20:56   ` Bart Van Assche
2017-09-15 20:56     ` Bart Van Assche
2017-09-15 21:06   ` Bart Van Assche
2017-09-15 21:06     ` Bart Van Assche
2017-09-15 21:42   ` Bart Van Assche
2017-09-15 21:42     ` Bart Van Assche

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=1505747894.2685.6.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=axboe@fb.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@infradead.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=loberman@redhat.com \
    --cc=martin.petersen@oracle.com \
    --cc=ming.lei@redhat.com \
    --cc=sagi@grimberg.me \
    --cc=snitzer@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.