Re: [ovs-dev] [PATCH] vswitchd: Always configure a default queue for QoS.

2012-02-16 Thread Ben Pfaff
On Thu, Feb 16, 2012 at 02:10:02PM -0800, Ethan Jackson wrote: > > Please argue out the situation with yourself and get back to me when > > you've come to a conclusion. > > After an intense bout of self directed parliamentary wrangling > (back-room deals, filibusters, ear marks, late night socrati

Re: [ovs-dev] [PATCH] vswitchd: Always configure a default queue for QoS.

2012-02-16 Thread Ethan Jackson
> Please argue out the situation with yourself and get back to me when > you've come to a conclusion. After an intense bout of self directed parliamentary wrangling (back-room deals, filibusters, ear marks, late night socratic dialectics) I've come to the following conclusion: HFSC drops packets

Re: [ovs-dev] [PATCH] vswitchd: Always configure a default queue for QoS.

2012-02-15 Thread Ben Pfaff
On Tue, Feb 14, 2012 at 11:45:17PM -0800, Ethan Jackson wrote: > > +        (Before version 1.6, Open vSwitch would drop all packets destined > > for > > +        the default queue if no configuration was present.) > > Are you sure this is true? My (admittedly fuzzy) memory tells me that > un-qu

Re: [ovs-dev] [PATCH] vswitchd: Always configure a default queue for QoS.

2012-02-14 Thread Ethan Jackson
> +        (Before version 1.6, Open vSwitch would drop all packets destined for > +        the default queue if no configuration was present.) Are you sure this is true? My (admittedly fuzzy) memory tells me that un-queued traffic effectively reduces the size of the pipe for the queued traffic.

[ovs-dev] [PATCH] vswitchd: Always configure a default queue for QoS.

2012-02-14 Thread Ben Pfaff
When an interface has QoS configured but no default queue (queue 0), OVS has until now installed that QoS configuration literally, which causes all packets destined for this default queue to be dropped. This behavior is usually both unexpected and undesirable. This commit changes behavior so that