On Tue, 2016-07-05 at 19:07 -0700, Alexei Starovoitov wrote: > > Great! Thanks for clarifying. > So then future netlink api is mandatory to drive this kernel patches? > How one can use this set without it?
The netlink API is to tweak things, it works reasonably well autonomously without it. > What is the main reason for this infra to be in the kernel instead of > userspace raw socket? Some interaction with the driver, right? > but it's not obvious from the patches. There are a few reasons. One it means we can use kernel level autoconfiguration like DHCP and NFS root which are quite handy when developing BMC stacks :-) Another one is that we haven't completely given up on reflecting the state of the remote NC-SI link into the "carrier status" of the local interface. We can't yet do it because the link monitor would stop the driver queues, but we could possibly invent a flag we set on the device that prevents this from happening and causes the queues to remain up even when the link appears down. This will be useful as some BMCs have multiple NICs that can all do NC-SI and thus we could have automatic fail over. Cheers, Ben.
