On Saturday, October 28, 2017 3:10 AM, Guan Junxiong wrote: >Does it mean some extra works such as: >1) showing the path topology of nvme multipath device Isn't connection to the target suppose guide the host to the shortest and fastest path available path or so called most optimized path. Sysfs entry can easily store that as we store path related info over there. >2) daemon to implement immediate and delayed failback This is also based on target, whenever target is ready for immediate or delayed failback it will let the connect from host succeed. Until then host is in reconnecting state across all path until it finds an optimized or un-optimized path. Why is this extra daemon needed ? >4) grouping paths besides ANA Why we cannot use NS Group here. Would be good idea to move away from legacy way of doing things for NVME devices. NVME Multipath implementation by Christoph is very simple. How about not making it super complicated. Best regards, Anish
