Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1565152
| From | Paolo Valente <paolo.valente@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCHSET v4] blk-mq-scheduling framework |
| Date | 2017-01-23 18:10 +0100 |
| Message-ID | <t2QhZ-Jd-43@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <sRdtD-2JG-9@gated-at.bofh.it> <t0zEC-63y-13@gated-at.bofh.it> <t0zEC-63y-11@gated-at.bofh.it> <t117Q-6i2-19@gated-at.bofh.it> <t2QhZ-Jd-45@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
> Il giorno 18 gen 2017, alle ore 17:21, Jens Axboe <axboe@fb.com> ha scritto: > > On 01/18/2017 08:14 AM, Paolo Valente wrote: >> according to the function blk_mq_sched_put_request, the >> mq.completed_request hook seems to always be invoked (if set) for a >> request for which the mq.put_rq_priv is invoked (if set). > > Correct, any request that came out of blk_mq_sched_get_request() > will always have completed called on it, regardless of whether it > had IO started on it or not. > It seems that some request, after being dispatched, happens to have no mq.put_rq_priv invoked on it now or then. Is it expected? If it is, could you point me to the path through which the end of the life of such a request is handled? Thanks, Paolo > -- > Jens Axboe >
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCHSET v4] blk-mq-scheduling framework Paolo Valente <paolo.valente@linaro.org> - 2017-01-17 12:00 +0100
Re: [PATCHSET v4] blk-mq-scheduling framework Paolo Valente <paolo.valente@linaro.org> - 2017-01-18 17:20 +0100
Re: [PATCHSET v4] blk-mq-scheduling framework Paolo Valente <paolo.valente@linaro.org> - 2017-01-23 18:10 +0100
Re: [PATCHSET v4] blk-mq-scheduling framework Paolo Valente <paolo.valente@linaro.org> - 2017-01-25 09:50 +0100
Re: [PATCHSET v4] blk-mq-scheduling framework Paolo Valente <paolo.valente@linaro.org> - 2017-01-26 15:30 +0100
csiph-web