diff options
author | Ming Lei <[email protected]> | 2017-02-22 18:14:00 +0800 |
---|---|---|
committer | Jens Axboe <[email protected]> | 2017-03-08 09:56:12 -0700 |
commit | 7ea5fe31c12dd8bcf4a9c5a4a7e8e23826a9a3b8 (patch) | |
tree | 6a9e862fb8ceccf5c64663630d5c2df1f5535656 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 737f98cfe7de8df7433a4d846850aa8efa44bd48 (diff) |
blk-mq: make lifetime consitent between q/ctx and its kobject
Currently from kobject view, both q->mq_kobj and ctx->kobj can
be released during one cycle of blk_mq_register_dev() and
blk_mq_unregister_dev(). Actually, sw queue's lifetime is
same with its request queue's, which is covered by request_queue->kobj.
So we don't need to call kobject_put() for the two kinds of
kobject in __blk_mq_unregister_dev(), instead we do that
in release handler of request queue.
Signed-off-by: Ming Lei <[email protected]>
Tested-by: Peter Zijlstra (Intel) <[email protected]>
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions