RE: [RFC-V2 PATCH 4/5] iscsi_transport: show network configuration in sysfs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> -----Original Message-----
> From: open-iscsi@xxxxxxxxxxxxxxxx [mailto:open-iscsi@xxxxxxxxxxxxxxxx]
> On Behalf Of Mike Christie


<snip>

> ccing Broadcom devs, Some questions for you guys below
> 
> 
> On 04/02/2011 01:34 PM, vikas.chaudhary@xxxxxxxxxx wrote:
> > From: Vikas Chaudhary<vikas.chaudhary@xxxxxxxxxx>
> >
> > To support multiple network addresses per adapter need to have a new
> way to
> > represent network interface (net iface) in sysfs.
> >
> > Currently only one ipaddress and hwaddress is displayed
> >
> > \# ls /sys/class/iscsi_host/host18
> > device  hwaddress  initiatorname  ipaddress  power  subsystem  uevent
> >
> > In this patch the net iface is presented as a separate class device.
> > The one that can be added/removed dynamically or statically, based on
> how
> > the user configures the multiple net iface on the adapter.
> >
> > The new sysfs directory would look like this
> > \# /sys/class/iscsi_iface/
> > |
> > |- ipv4-iface-<host_no>-<iface_no>/<-- for ipv4
> >                                  |- ipaddress
> >                                  |- subnet
> >                                  |- gateway
> >                                  |- bootproto
> >                                  |- state
> > |- ipv6-iface-<host_no>-<iface_no>/<-- for ipv6
> >                                  |- ipaddress
> >                                  |- link_local_addr
> >                                  |- router_addr
> >                                  |- ipaddr_autocfg
> >                                  |- linklocal_autocfg
> >                                  |- state
> >
> 
> 
> With patch "[RFC-V2 PATCH 1/5] iscsi_transport: add support for
> set_net_config" userspace would send down the vlan info.

How can this converged adapter separate vlans created via ip on the network function from vlans created via iSCSI function vs vlan created on the FCoE function?

> 
> If we add a vlan sysfs file to the iscsi_iface, to export the info was
> bnx2i going call iscsi_create_iface for each vlan? If so I am not sure
> what bnx2i will use for the iface_num. It is supposed to be persistent,
> right?
> 

Would iscsiadm be used to create the vlan.. This would be introducing another way to create vlans..

--
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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux