scsi_dh framework update
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest7 patches 31 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | scsi_dh: Implement generic device table handlingdrivers/ drivers/ drivers/ +2 more | +300 | 3 replies | |
| 2/7 | scsi_dh: Add 'dh_state' sysfs attributedrivers/ | +88 | 2 replies | |
| 3/7 | scsi_dh: add generic SPC-3 alua handlerdrivers/ drivers/ drivers/ +2 more | +820 | 5 replies | |
| 4/7 | scsi_dh: Update EMC handlerdrivers/ | +340 | 3 replies | |
| 5/7 | scsi_dh: Update hp_sw hardware handlerdrivers/ | +225 | 1 reply | |
| 6/7 | scsi_dh: Update RDAC device handlerdrivers/ | +53 | 3 replies | |
| 7/7 | scsi_dh: attach to hardware handler from dm-mpathdrivers/ drivers/ include/ | +59 | 13 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/7] scsi_dh framework update
Hi James,
this is a repost of my patchset to update the scsi_dh infrastructure.
It's based on the current scsi-misc tree.
Main features of the patchset are:
- Use a single callback for the notifier chain
- Merge all device maps into a single list, which will be scanned by a generic function
- Add a sysfs attribute 'dh_state' for each sdev
- Add a generic SPC-3 ALUA device handler
- Update device handlers to check if the device actually supports this handler. When attaching manually we are able to attach to basically any device, so we have to make sure that the device handler is actually supported.
- Manually attach a device when a hardware handler is specified; this allows multipath to override the built-in hardware table.
As per usual, comment etc are welcome.
Cheers,
Hannes
Signature · 8 lines
Dr. Hannes Reinecke zSeries & Storage [email protected] +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html