> > > > I think ideally we would like to get to that stage (i.e. be able to > > tell that a datapath supports a particular port type). I can't think > > of a way off-hand to do that by probing. I think it would have to be > > done by a list that could be modified by updating the code and recompiling. > > 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?
Both port and datapath types are importance for this use case. We could perhaps have ovsdb report something more structured (i.e. report what port types are supported with what netdev types) but I am not sure of a way to do this other than hardcoding this information in each datapath which I don't think is great. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
