Ben, Thanks for your clarification.
The QoS in OVS is applied at interface level even though it is applied at port level from command line interface. So, in case of bonding interfaces, it applies to all the underlying bonding interfaces of a port. On Mon, Mar 11, 2013 at 11:35 PM, Ben Pfaff <[email protected]> wrote: > On Mon, Mar 11, 2013 at 06:00:21PM +0530, Jagadish Nadimpalli wrote: > > In openvswitch, an interface is nothing but a "netdev". A port can have a > > single interface associated with it or multiple interfaces in case of > > bonding. Now, when it comes to applying QoS policies, the ingress > policing > > is applied to an interface where as the port level QoS has the egress > > Queues and egress rate limiting. > > > > I understood that the reason for *"applying ingress rate limiting on > > interface"* is because the traffic is first seen by the actual netdev and > > then the vswitch takes actions later.* *And the reason for *"applying > > egress rate limiting on port"* is because the traffic is first seen by > the > > vswitch port (not the interface). Could you please confirm if my > > understanding is correct. > > The reason to apply egress rate limiting to ports (instead of > interfaces) is mostly because we would like to at some point provide > QoS across an entire bond rather than on the individual interfaces. > That's hard, so for now although we put the QoS configuration on the > port, it actually applies individually to the interfaces. >
_______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
