aboutsummaryrefslogtreecommitdiff
path: root/Kbuild
diff options
context:
space:
mode:
authorGravatar Jens Axboe <axboe@fb.com> 2016-03-30 10:21:08 -0600
committerGravatar Jens Axboe <axboe@fb.com> 2016-11-05 17:09:53 -0600
commitd278d4a8892f13b6a9eb6102b356402f0e062324 (patch)
tree2d1f9dc740b6d47257404c02292493568c8ee656 /Kbuild
parentblk-mq: immediately dispatch big size request (diff)
downloadlinux-d278d4a8892f13b6a9eb6102b356402f0e062324.tar.gz
linux-d278d4a8892f13b6a9eb6102b356402f0e062324.tar.bz2
linux-d278d4a8892f13b6a9eb6102b356402f0e062324.zip
block: add code to track actual device queue depth
For blk-mq, ->nr_requests does track queue depth, at least at init time. But for the older queue paths, it's simply a soft setting. On top of that, it's generally larger than the hardware setting on purpose, to allow backup of requests for merging. Fill a hole in struct request with a 'queue_depth' member, that drivers can call to more closely inform the block layer of the real queue depth. Signed-off-by: Jens Axboe <axboe@fb.com> Reviewed-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions