We introduced the rtnl_link API to avoid having each driver
come up with its own method of creating virtual network devices.
Besides the fact that it is the interface intended to be used
for this kind of thing and the advantages mentioned in my
response to Roland, looking at your interface, there are a
few more advantages from integrating this cleanly in iproute:
> +echo -n 00066a01de000037 >
/sys/class/infiniband_qlgc_vnic/interfaces/veth1/primary_path/ioc_guid
> +echo -n fe8000000000000100066a11de000037 >
/sys/class/infiniband_qlgc_vnic/interfaces/veth1/primary_path/dgid
> +echo -n ffff >
/sys/class/infiniband_qlgc_vnic/interfaces/veth1/primary_path/pkey
I guess life would be easier for users if those parameters can
be generated in userspace or at least looked up in something
like the maps in /etc/iproute2/.
> +echo -n 100 >
/sys/class/infiniband_qlgc_vnic/interfaces/veth1/primary_path/heartbeat
I assume thats some kind of timing parameter. iproute
would allow to specify the (undocumented) unit and convert
it appropriately.
In any case, things like tx_csum and rx_csum definitely do
not belong in this interface.
Sorry, that wasn't meant seriously :)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html