>-----Original Message----- >From: open-iscsi@xxxxxxxxxxxxxxxx [mailto:open-iscsi@xxxxxxxxxxxxxxxx] On >Behalf Of Mike Christie >Sent: Wednesday, April 13, 2011 10:14 PM >To: open-iscsi@xxxxxxxxxxxxxxxx >Cc: Vikas Chaudhary; James.Bottomley@xxxxxxx; linux-scsi@xxxxxxxxxxxxxxx; >Lalit Chandivade; Ravi Anand; Jayamohan.Kallickal@xxxxxxxxxx >Subject: Re: [RFC-V2 PATCH 4/5] iscsi_transport: show network configuration >in sysfs > >On 04/13/2011 09:48 AM, Vikas Chaudhary wrote: >> >> >>> -----Original Message----- >>> From: Mike Christie [mailto:michaelc@xxxxxxxxxxx] >>> Sent: Wednesday, April 13, 2011 10:11 AM >>> To: Vikas Chaudhary >>> Cc: James.Bottomley@xxxxxxx; linux-scsi@xxxxxxxxxxxxxxx; open- >>> iscsi@xxxxxxxxxxxxxxxx; Lalit Chandivade; Ravi Anand; >>> Jayamohan.Kallickal@xxxxxxxxxx >>> Subject: Re: [RFC-V2 PATCH 4/5] iscsi_transport: show network >configuration >>> in sysfs >>> >>> On 04/12/2011 11:23 PM, Mike Christie wrote: >>>> Do we want to make the kernel iscsi iface more generic or maybe just >>>> rename it to reflect it is just based on net settings? >>>> >>>> The issue with making it more generic is that with the current drivers, >>>> we do not care what info like the initiatorname in the kernel code. >That >>>> is all handled in userspace because all the session management is >there, >>>> so there is no point in adding that complexity here. >>> >>> I take part of this back. We set the iscsi iface name and initiator name >>> on the session right now. We need that info for relogin type of >>> situations where iscsid might have died and we need to know the >>> initiatorname to use. We cannot read it from a disk, because that disk >>> might be the one are are relogging into. >>> >>> It might not hurt to make the kernel's iscsi ifaces abstraction more >>> general. >> >> Yes and also to reflect correct status of network settings it will be >> good to have iscsi_iface in the kernel. This is useful in a case where >> user set DHCP settings then we can reflect IP addresses and other >> settings in the kernel iface. >> > >How come you did not export some values like the vlan in the iscsi iface? > Currently we have partial implementation of VLAN. iscsi_transport supports VLAN set operation but we need to implement this in iscsiadm and export VLAN to sysfs iface. We will add this support in our next patches. This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
