diff options
| author |   Ming Lei <ming.lei@redhat.com> | 2024-02-28 12:08:57 +0800 |
|---|---|---|
| committer |   Jens Axboe <axboe@kernel.dk> | 2024-02-28 07:22:06 -0700 |
| commit | ec30b461f3d067bd322a6c3a6c5105746ed9bf14 (patch) | |
| tree | f6e65bf1c333892dca5d08e61c943067fcc1d873 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | ubd: open the backing files in ubd_add (diff) | |
| download | wireguard-linux-ec30b461f3d067bd322a6c3a6c5105746ed9bf14.tar.xz wireguard-linux-ec30b461f3d067bd322a6c3a6c5105746ed9bf14.zip | |
blk-mq: don't change nr_hw_queues and nr_maps for kdump kernel
For most of ARCHs, 'nr_cpus=1' is passed for kdump kernel, so
nr_hw_queues for each mapping is supposed to be 1 already.
More importantly, this way may cause trouble for driver, because blk-mq and
driver see different queue mapping since driver should setup hardware
queue setting before calling into allocating blk-mq tagset.
So not overriding nr_hw_queues and nr_maps for kdump kernel.
Cc: Wen Xiong <wenxiong@us.ibm.com>
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Link: https://lore.kernel.org/r/20240228040857.306483-1-ming.lei@redhat.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions