On Wed, Jun 4, 2014 at 2:48 AM, Tahhan, Maryam <maryam.tah...@intel.com> wrote: > Hi Pravin > Are you suggesting adding the dpdk-vhost interface code into netdev-dpdk.c, > defining a common netdev_class and working from there (similar to > netdev-linux and tap devices etc.)? > It does break up modularity somewhat in that vhost ports are logical and > distinct from dpdk ports, but it can be done. Or would abstracting out what > is common into a set of functions that dpdk ports (logical/physical) can use > be more suitable? >
I agree vhost are logically different but since both are poll mode device they do share device some functionality. So you can keep vhost in separate file and share functions and structures from netdev-dpdk. Thanks, Pravin. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
