aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf
diff options
context:
space:
mode:
authorBrian King <[email protected]>2024-09-03 08:47:09 -0500
committerMartin K. Petersen <[email protected]>2024-09-12 20:18:30 -0400
commite3684006945414153a33c5c4d1202dda2b80650f (patch)
tree49a6efd8358351ca57b872965a076370ae8e2c2d /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf
parentb112947ffc30e9632d5c2acd0e9081e3e6bee01e (diff)
scsi: ibmvfc: Add max_sectors module parameter
There are some scenarios that can occur, such as performing an upgrade of the virtual I/O server, where the supported max transfer of the backing device for an ibmvfc HBA can change. If the max transfer of the backing device decreases, this can cause issues with previously discovered LUNs. This patch accomplishes two things. First, it changes the default ibmvfc max transfer value to 1MB. This is generally supported by all backing devices, which should mitigate this issue out of the box. Secondly, it adds a module parameter, enabling a user to increase the max transfer value to values that are larger than 1MB, as long as they have configured these larger values on the virtual I/O server as well. [mkp: fix checkpatch warnings] Signed-off-by: Brian King <[email protected]> Link: https://lore.kernel.org/r/[email protected] Reviewed-by: Martin Wilck <[email protected]> Reviewed-by: Hannes Reinecke <[email protected]> Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf')
0 files changed, 0 insertions, 0 deletions