> The sysadmin creates "for iwarp use only" alias interfaces of the form
> "devname:iw*" where devname is the native interface name (eg eth0) for the
> iwarp netdev device. The alias label can be anything starting with "iw".
> The "iw" immediately after the ':' is the key used by the iwarp driver.
What's wrong with my suggestion of having the iwarp driver create an
"iwX" interface to go with the normal "ethX" interface? It seems
simpler to me, and there's a somewhat similar precedent with how
mac80211 devices create both wlan0 and wmaster0 interfaces.
- R.
Roland Dreier wrote:
> The sysadmin creates "for iwarp use only" alias interfaces of the form
> "devname:iw*" where devname is the native interface name (eg eth0) for the
> iwarp netdev device. The alias label can be anything starting with "iw".
> The "iw" immediately after the ':' is the key used by the iwarp driver.
What's wrong with my suggestion of having the iwarp driver create an
"iwX" interface to go with the normal "ethX" interface? It seems
simpler to me, and there's a somewhat similar precedent with how
mac80211 devices create both wlan0 and wmaster0 interfaces.
- R.
It seemed much more painful for me to implement. :-)
I'll look into this, but I think for this to be done, the changes must
be in the cxgb3 driver, not the rdma driver, because the guts of the
netdev struct are all private to cxgb3. Remember that this interface
needs to still do non TCP traffic (like ARP and UDP)...
Maybe you have something in mind here that I'm not thinking about?
Steve.