On 09/12/2015 02:45, "Gray, Mark D" <mark.d.g...@intel.com> wrote:
>> From: Justin Pettit [mailto:jpet...@ovn.org] >> Sent: Tuesday, December 8, 2015 5:03 PM >> >> > On Dec 8, 2015, at 1:01 AM, Gray, Mark D <mark.d.g...@intel.com> >>wrote: >> > >> >> +Feature | Linux upstream | Linux OVS tree | Userspace >>| Hyper-V >> | >> >> >>+----------------------|:--------------:|:--------------:|:---------:|:- >> >> +----------------------|------:| >> >> +Connection tracking | 4.3 | 3.10 | NO >>| NO | >> >> +Tunnel - LISP | NO | YES | NO >>| NO | >> >> +Tunnel - STT | NO | 3.5 | NO >>| YES | >> >> +Tunnel - GRE | 3.11 | YES | YES >>| NO | >> >> +Tunnel - VXLAN | 3.12 | YES | YES >>| YES | >> >> +Tunnel - Geneve | 3.18 | YES | YES >>| NO | >> >> +QoS | YES | YES | NO >>| NO | >> > >> > [Gray, Mark D] >> > QoS is such a loaded term. It may be good to expand on this a bit. >> >> What about breaking it into "Traffic Policing" and "Traffic Shaping"? >>Those >> are the two dimensions we usually focus on. > >That helps. There is also Ingress Policing in the other direction and >the metering work being done by Jarno. > >All this might make the table quite complicated though! Good point Mark, I've split this into Policing and Shaping for now, following Justin's advice. I didn't include meters because none of the datapaths supports them currently. I think we should add a row when the implementation is merged. > > >> >> --Justin >> >> > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
