diff options
| author | Christoph Hellwig <[email protected]> | 2024-03-04 14:04:59 +0000 |
|---|---|---|
| committer | Keith Busch <[email protected]> | 2024-03-04 16:24:56 +0000 |
| commit | c5be5df7217fec219e1be063859e5d099b6a9227 (patch) | |
| tree | ffde8317969870ca051da25b7cc70fbd399922d4 /tools/perf/scripts/python/sctop.py | |
| parent | nvme: use the atomic queue limits update API (diff) | |
| download | kernel-c5be5df7217fec219e1be063859e5d099b6a9227.tar.gz kernel-c5be5df7217fec219e1be063859e5d099b6a9227.zip | |
nvme-multipath: pass queue_limits to blk_alloc_disk
The multipath disk starts out with the stacking default limits.
The one interesting part here is that blk_set_stacking_limits
sets the max_zone_append_sectorts to UINT_MAX, which fails the
validation for non-zoned devices. With the old one call per
limit scheme this was fine because no one verified this weird
mismatch and it was fixed by blk_stack_limits a little later
before I/O could be issued.
Signed-off-by: Christoph Hellwig <[email protected]>
Signed-off-by: Keith Busch <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/sctop.py')
0 files changed, 0 insertions, 0 deletions