diff options
author | Jens Axboe <axboe@fb.com> | 2014-09-10 09:02:03 -0600 |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2014-09-10 09:02:03 -0600 |
commit | a516440542afcb9647f88d12c35640baf02d07ea (patch) | |
tree | d6e1cdc5f18f6c8025d4fb6415e682bb0b60dd29 /block/blk-core.c | |
parent | df35c7c912fe668797681842b3b74c61b0664050 (diff) | |
download | linux-stable-a516440542afcb9647f88d12c35640baf02d07ea.tar.gz linux-stable-a516440542afcb9647f88d12c35640baf02d07ea.tar.bz2 linux-stable-a516440542afcb9647f88d12c35640baf02d07ea.zip |
blk-mq: scale depth and rq map appropriate if low on memory
If we are running in a kdump environment, resources are scarce.
For some SCSI setups with a huge set of shared tags, we run out
of memory allocating what the drivers is asking for. So implement
a scale back logic to reduce the tag depth for those cases, allowing
the driver to successfully load.
We should extend this to detect low memory situations, and implement
a sane fallback for those (1 queue, 64 tags, or something like that).
Tested-by: Robert Elliott <elliott@hp.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'block/blk-core.c')
0 files changed, 0 insertions, 0 deletions