diff options
| author | Mike Snitzer <[email protected]> | 2018-03-05 19:10:11 +0000 |
|---|---|---|
| committer | Mike Snitzer <[email protected]> | 2018-03-07 01:23:58 +0000 |
| commit | 8d47e65948ddea4398892946d9e50778a316b397 (patch) | |
| tree | cb699eae23c76bd9378e2e75de250e545b9ee2ad /scripts/gcc-plugins/cyc_complexity_plugin.c | |
| parent | dm table: fix "nvme" test (diff) | |
| download | kernel-8d47e65948ddea4398892946d9e50778a316b397.tar.gz kernel-8d47e65948ddea4398892946d9e50778a316b397.zip | |
dm mpath: remove unnecessary NVMe branching in favor of scsi_dh checks
This eliminates the "queue_mode" configuration's "nvme" mode. There
wasn't anything NVMe-specific about that mode. It was named "nvme"
because it was a short name for the mode. But the entire point of the
mode was to optimize the multipath target for underlying devices that
are _not_ SCSI-based. Devices that aren't SCSI have no need for the
various SCSI device handler (scsi_dh) specific code in DM multipath.
But rather than narrowly define this scsi_dh vs not branching in terms
of "nvme": invert the logic so that we're just checking whether a
multipath device is layered on SCSI devices with scsi_dh attached.
This allows any future storage technology to avoid scsi_dh specific code
in the multipath target too.
Fixes: 848b8aefd4 ("dm mpath: optimize NVMe bio-based support")
Suggested-by: Mikulas Patocka <[email protected]>
Signed-off-by: Mike Snitzer <[email protected]>
Diffstat (limited to 'scripts/gcc-plugins/cyc_complexity_plugin.c')
0 files changed, 0 insertions, 0 deletions