On Mon, Mar 16, 2015 at 01:53:21PM +0000, Gray, Mark D wrote: > > > > > > > > I'm pretty reluctant to put in something that we know would have to > > > > be refined, given that refining it would either have to add > > > > duplicate information to the schema (e.g. some additional mapping > > > > from datapath type to port > > > > types) or be backward incompatible (e.g. deleting the list of port > > > > types). > > > > What if we just started out with the list of datapath types? > > > > > > We would like to be able to tell that the vswitch instance is capable > > > of adding dpdk type ports. If we only show the datapaths we are unable > > > to tell if that is the case as the netdev datapath can also be used > > > without > > dpdk. > > > > So it's a matter of making the controller know that it can essentially turn > > on a > > "turbo mode" by setting the interface type to dpdk? If so, have you > > considered coming up with a way to make dpif-netdev use dpdk netdevs > > automatically when DPDK is compiled in and available for a given netdev? > > (Is > > it feasible?) > > Yes. Openstack needs to know if a bridge can use dpdk ports before Neutron > sets up ports by running ovs-vsctl. > > Are you saying that it should automatically use a dpdk port in favour > of a std linux one?
I guess OVS would need to automatically choose not just the port type but the datapath type, which seems like a bad idea. OK, let's drop that idea. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
