On Tuesday 03 August 2010, John Fastabend wrote: > Jens Osterkamp wrote: > > This code receives a IEEE 802.1Qbg virtual station instance from libvirt in > > a SETLINK message. The parsed VSI is then handed over to VDP for processing. > > The VDP state machine processes the VSI while libvirt polls the result using > > GETLINK. > > > > Requires at least Linux kernel 2.6.35-rc1. > > > > Signed-off-by: Jens Osterkamp <jens@xxxxxxxxxxxxxxxxxx> > > Signed-off-by: Gerhard Stenzel <gstenzel@xxxxxxxxxxxxxxxxxx> > > Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx> > > --- > > event_iface.c | 617 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++- > > lldp_vdp.c | 2 +- > > lldpad.c | 10 + > > 3 files changed, 622 insertions(+), 7 deletions(-) > > > > Jens, > > Can you explain why this interface is needed? There is already a kernel We needed a way in libvirt to associate the virtual network interface(s) of a guest with an adjacent switch. The protocol to do this could be implemented both in userspace (e.g. in lldpad) or in the adapter firmware. You could have different drivers for both ways in libvirt but to keep it simple we decided to use netlink for both. The original mailthread on netdev started here http://marc.info/?l=linux-netdev&m=127242976205746&w=2 > interface for this how come libvirt and lldpad can not use the kernel interface? In fact we are using the kernel interface for this, e.g. the definitions of the netlink attributes are in the kernel header files. The only difference is that in the userspace case, the netlink messages are addressed to the pid of lldpad whereas in the firmware case, the netlink messages go to pid 0 (kernel). Best regards, Jens Osterkamp -------------------------------------------------------------------------------- IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization