nvme-cli: nvmf auto-connect scripts
Get series with b4
b4 am [email protected]Versions newest first
- v3 Latest0 of 10 patches 0 repliesNew
Patches in v3 No applies recorded yet
None of the 10 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH v3 00/10] nvme-cli: nvmf auto-connect scripts
Quoted 23 lines · James Smart
This is a formal posting of the patches, not an RFC.
This posting is a combination of the RFC postings of nvme-fc auto-connect scripts by Hannes, Sagi, and I. The auto-connect scripts are utilized on nvme-fc and for persistent discovery controllers that send AENs. It does not contain the code that handles the persistent discovery controller AEN and generates the event.
The auto-connect scripts are now commonized with the exception of the nvme-fc boot connections service. It's expected that both the persistent discovery controllers and nvme-fc can post the same udev event. Whenever the discovery aen generates an event, the new --device=<name> argument will be used to identify the persistent discovery controller. When --device is used, the other connect attributes will be specified, set to the values of the discovery controller, and will be used by the cli to validate the device is who it should be or a new discovery controller will be created. When nvme-fc generates it's events, it will specify --device=none and specify the discovery controller addressing arguments. If a persistent discovery controller exists on nvme-fc, will do nothing special and AEN's from it will follow the --device=<name> syntax.
Quoted 6 lines
The udev event handler supports both the new event to be used by discovery controllers as well as the existing nvme-fc transport event. The nvme-fc transport will be migrated to issue the new event syntax. The udev script will continue to support the older style nvme-fc event info in case the cli is running against an older kernel.
Series looks good to me, patches applied.
We've a lot of new stuff now, I'll plan to tag a release within the next week if I don't observe or hear of any alarming issues.