Re: [PATCH 11/14] scsi: unwind blk_end_request_all and blk_end_request_err calls

Christoph == Christoph Hellwig h...@lst.de writes: Christoph Replace the calls to the various blk_end_request variants Christoph with opencode equivalents. Blk-mq is using a model that Christoph gives the driver control between the bio updates and the Christoph actual completion, and making the

[PATCH 11/14] scsi: unwind blk_end_request_all and blk_end_request_err calls

Replace the calls to the various blk_end_request variants with opencode equivalents. Blk-mq is using a model that gives the driver control between the bio updates and the actual completion, and making the old code follow that same model allows us to keep the code more similar for both paths.

Re: [PATCH 11/14] scsi: unwind blk_end_request_all and blk_end_request_err calls

On 06/25/2014 06:51 PM, Christoph Hellwig wrote: Replace the calls to the various blk_end_request variants with opencode equivalents. Blk-mq is using a model that gives the driver control between the bio updates and the actual completion, and making the old code follow that same model allows us

[PATCH 11/14] scsi: unwind blk_end_request_all and blk_end_request_err calls

Replace the calls to the various blk_end_request variants with opencode equivalents. Blk-mq is using a model that gives the driver control between the bio updates and the actual completion, and making the old code follow that same model allows us to keep the code more similar for both pathes.

[PATCH 11/14] scsi: unwind blk_end_request_all and blk_end_request_err calls

Replace the calls to the various blk_end_request variants with opencode equivalents. Blk-mq is using a model that gives the driver control between the bio updates and the actual completion, and making the old code follow that same model allows us to keep the code more similar for both pathes.