Hi, I am exploring creating a new vport type for a zeroconf virtual network (similar to a multicast GRE tunnel) So far I have reviewed most of the kernel module code and have worked out how to create a new vport (adding to vport.c struct, defining vport in vport.h and creating vport-newport.c) but when reviewing vport-gre.c I noticed tunnel.c/.h which seems to be all of the IP resolution, transmission stuff etc.
My new vport will probably be using Infinband ibverbs rather than IP as the transport network for tunneled packets. Would it be better to extend tunnel.c to handle native Infinband and define a new protocol IB_<type> in tunnel.h or just build everything into vport-newport.c? Also if there is anything else I should know about implementing a new vport that would be awesome to know too. :) Joseph. -- * Founder | Director | VP Research Orion Virtualisation Solutions* | www.orionvm.com.au | Phone: 1300 56 99 52 | Mobile: 0428 754 846
_______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
