On Fri, 2018-08-10 at 09:59 +-0800, jianchao.wang wrote: +AD4- On 08/10/2018 03:41 AM, Bart Van Assche wrote: +AD4- +AD4- Instead of scheduling runtime resume of a request queue after a +AD4- +AD4- request has been queued, schedule asynchronous resume during request +AD4- +AD4- allocation. The new pm+AF8-request+AF8-resume() calls occur after +AD4- +AD4- blk+AF8-queue+AF8-enter() has increased the q+AF8-usage+AF8-counter request queue +AD4- +AD4- +AF4AXgBeAF4AXgBeAF4AXgBeAF4AXgBeAF4AXgBeAF4AXgBeAF4AXgBeAF4AXgBeAF4AXgBeAF4AXgBeAF4AXgBeAF4AXgBeAF4AXgBeAF4AXgBeAF4- +AD4- +AD4- member. This change is needed for a later patch that will make request +AD4- +AD4- allocation block while the queue status is not RPM+AF8-ACTIVE. +AD4- +AD4- Is it +ACI-after getting q-+AD4-q+AF8-usage+AF8-counter fails+ACI- ? +AD4- And also this blk+AF8-pm+AF8-request+AF8-resume will not affect the normal path. +ADs-) Right, the commit message needs to be brought in sync with the code. Bart.
