Hi, On Fri, Nov 6, 2015 at 1:53 PM, srujan k <[email protected]> wrote:
> Hi All, > Why zebra choses netlink sockets to update kernel routing table.Why not > ioctl or others? Is it because of netlink sockets available to all flavours > of linux. > AFAIK Its because Netlink interface is more cleaner than ioctls. Passing more information or any attribute to kernel would just be addition of netlink attribute and on the other hand to extend ioctls, a new type to the struct that's passed between user space and kernel space should be added which causes more problems, there could be more to this. > Is there any performance degrade of using other IPC mechanism between > kernel and zebra daemon? > This has its own overhead but the daemons run on User space, so you need a mechanism to send the information down and i am not sure if there is any other way out for this. > > What mechanism will be used by vendors like juniper, citrix and cisco to > update routing tables? > I am not sure what others use but as far as i know IOS and JunOS are based out of BSDs so they should be using something of this sort. But this is just a speculation. I am not sure of this. > > Regards, > Srujan > > _______________________________________________ > Quagga-dev mailing list > [email protected] > https://lists.quagga.net/mailman/listinfo/quagga-dev >
_______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
