Re: [PATCH V4 0/3] blk-mq: issue request directly for blk_insert_cloned_request

2018-01-15 Thread Ming Lei
On Mon, Jan 15, 2018 at 12:43:44PM -0500, Mike Snitzer wrote: > On Mon, Jan 15 2018 at 11:58am -0500, > Ming Lei wrote: > > > Hi Guys, > > > > The 3 paches changes the blk-mq part of blk_insert_cloned_request(), > > in which we switch to blk_mq_try_issue_directly(), so that both dm-rq > > and bl

Re: [PATCH V4 0/3] blk-mq: issue request directly for blk_insert_cloned_request

2018-01-15 Thread Mike Snitzer
On Mon, Jan 15 2018 at 11:58am -0500, Ming Lei wrote: > Hi Guys, > > The 3 paches changes the blk-mq part of blk_insert_cloned_request(), > in which we switch to blk_mq_try_issue_directly(), so that both dm-rq > and blk-mq can get the dispatch result of underlying queue, and with > this informat

[PATCH V4 0/3] blk-mq: issue request directly for blk_insert_cloned_request

2018-01-15 Thread Ming Lei
Hi Guys, The 3 paches changes the blk-mq part of blk_insert_cloned_request(), in which we switch to blk_mq_try_issue_directly(), so that both dm-rq and blk-mq can get the dispatch result of underlying queue, and with this information, blk-mq can handle IO merge much better, then sequential I/O per