Rishi Srivatsavai wrote:
Sebastien Roy wrote:
TRILL IS-IS daemon (trilld) uses libdladm to access bridge instance
configuration. trilld determines the data links that are part of the
RBridge instance from libdladm and also retrieves link properties such
as the default VLAN tag of the link using libdladm.
So if it's already using libdladm to get some information on the links
it uses, then why would you need these special ioctls?
TRILL_HWADDR
TRILL_GETMTU
These are generic link attributes that can be obtained through libdladm
as well.
True, I think these ioctls were introduced in AF_TRILL prior to the use of
libdladm for link configuration. I will investigate and see if we can
avoid introducing them.
I think TRILL_GETMTU is needed so that the trill kernel module can
provide the *proper* TRILL-related MTU information to the IS-IS daemon.
It's unfortunately not simple, and isn't just the same as the datalink
layer.
TRILL_HWADDR has similar concerns. You can get the address(es) used on
a given link, but VNICs in use might make the correct address
determination a bit harder. (At least it seemed so the last time I
looked at it. Maybe that's no longer an issue ...)
--
James Carlson 42.703N 71.076W <[email protected]>
_______________________________________________
networking-discuss mailing list
[email protected]
