All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "snitzer@redhat.com" <snitzer@redhat.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>,
	"hch@infradead.org" <hch@infradead.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"axboe@fb.com" <axboe@fb.com>,
	"ming.lei@redhat.com" <ming.lei@redhat.com>,
	"loberman@redhat.com" <loberman@redhat.com>
Subject: Re: [PATCH 2/5] dm-mpath: return DM_MAPIO_REQUEUE in case of rq allocation failure
Date: Fri, 15 Sep 2017 20:48:56 +0000	[thread overview]
Message-ID: <1505508534.2417.9.camel@wdc.com> (raw)
In-Reply-To: <20170915200655.GA28136@redhat.com>

On Fri, 2017-09-15 at 16:06 -0400, Mike Snitzer wrote:
> The problem is that multipath_clone_and_map() is now treated as common
> code (thanks to both blk-mq and old .request_fn now enjoying the use of
> blk_get_request) BUT: Ming please understand that this code is used by
> old .request_fn too.  So it would seem that the use of
> DM_MAPIO_DELAY_REQUEUE vs DM_MAPIO_REQUEUE needs to be based on dm-sq vs
> dm-mq.

Hello Mike,

My proposal is to leave out patches 1 and 2 entirely. Since the SCSI core
calls blk_mq_run_hw_queues() anyway after a request has finished it is not
clear to me what the motivation was behind the development of patches 1 and
2 in this series. If the goal was to rerun a queue after a request has
finished I think the same approach should be taken for dm as for the SCSI
core, namely to run the queue from inside the end_io callback.

Bart.

WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "snitzer@redhat.com" <snitzer@redhat.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>,
	"hch@infradead.org" <hch@infradead.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"axboe@fb.com" <axboe@fb.com>,
	"ming.lei@redhat.com" <ming.lei@redhat.com>,
	"loberman@redhat.com" <loberman@redhat.com>
Subject: Re: [PATCH 2/5] dm-mpath: return DM_MAPIO_REQUEUE in case of rq allocation failure
Date: Fri, 15 Sep 2017 20:48:56 +0000	[thread overview]
Message-ID: <1505508534.2417.9.camel@wdc.com> (raw)
In-Reply-To: <20170915200655.GA28136@redhat.com>

T24gRnJpLCAyMDE3LTA5LTE1IGF0IDE2OjA2IC0wNDAwLCBNaWtlIFNuaXR6ZXIgd3JvdGU6DQo+
IFRoZSBwcm9ibGVtIGlzIHRoYXQgbXVsdGlwYXRoX2Nsb25lX2FuZF9tYXAoKSBpcyBub3cgdHJl
YXRlZCBhcyBjb21tb24NCj4gY29kZSAodGhhbmtzIHRvIGJvdGggYmxrLW1xIGFuZCBvbGQgLnJl
cXVlc3RfZm4gbm93IGVuam95aW5nIHRoZSB1c2Ugb2YNCj4gYmxrX2dldF9yZXF1ZXN0KSBCVVQ6
IE1pbmcgcGxlYXNlIHVuZGVyc3RhbmQgdGhhdCB0aGlzIGNvZGUgaXMgdXNlZCBieQ0KPiBvbGQg
LnJlcXVlc3RfZm4gdG9vLiAgU28gaXQgd291bGQgc2VlbSB0aGF0IHRoZSB1c2Ugb2YNCj4gRE1f
TUFQSU9fREVMQVlfUkVRVUVVRSB2cyBETV9NQVBJT19SRVFVRVVFIG5lZWRzIHRvIGJlIGJhc2Vk
IG9uIGRtLXNxIHZzDQo+IGRtLW1xLg0KDQpIZWxsbyBNaWtlLA0KDQpNeSBwcm9wb3NhbCBpcyB0
byBsZWF2ZSBvdXQgcGF0Y2hlcyAxIGFuZCAyIGVudGlyZWx5LiBTaW5jZSB0aGUgU0NTSSBjb3Jl
DQpjYWxscyBibGtfbXFfcnVuX2h3X3F1ZXVlcygpIGFueXdheSBhZnRlciBhIHJlcXVlc3QgaGFz
IGZpbmlzaGVkIGl0IGlzIG5vdA0KY2xlYXIgdG8gbWUgd2hhdCB0aGUgbW90aXZhdGlvbiB3YXMg
YmVoaW5kIHRoZSBkZXZlbG9wbWVudCBvZiBwYXRjaGVzIDEgYW5kDQoyIGluIHRoaXMgc2VyaWVz
LiBJZiB0aGUgZ29hbCB3YXMgdG8gcmVydW4gYSBxdWV1ZSBhZnRlciBhIHJlcXVlc3QgaGFzDQpm
aW5pc2hlZCBJIHRoaW5rIHRoZSBzYW1lIGFwcHJvYWNoIHNob3VsZCBiZSB0YWtlbiBmb3IgZG0g
YXMgZm9yIHRoZSBTQ1NJDQpjb3JlLCBuYW1lbHkgdG8gcnVuIHRoZSBxdWV1ZSBmcm9tIGluc2lk
ZSB0aGUgZW5kX2lvIGNhbGxiYWNrLg0KDQpCYXJ0Lg==

  reply	other threads:[~2017-09-15 20:48 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
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 [this message]
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=1505508534.2417.9.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=axboe@fb.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=loberman@redhat.com \
    --cc=ming.lei@redhat.com \
    --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.