Re: [ovs-dev] [PATCH 2/2] ofproto: Always set MTU for new internal ports.

2016-08-31 Thread Daniele Di Proietto
On 30/08/2016 18:06, "Daniele Di Proietto" wrote: > > > > > >On 30/08/2016 15:32, "Ben Pfaff" wrote: > >>On Tue, Aug 30, 2016 at 11:41:15AM -0700, Daniele Di Proietto wrote: >>> We only changed the MTU of new internal ports if it is bigger than the >>>

Re: [ovs-dev] [PATCH 2/2] ofproto: Always set MTU for new internal ports.

2016-08-30 Thread Daniele Di Proietto
On 30/08/2016 15:32, "Ben Pfaff" wrote: >On Tue, Aug 30, 2016 at 11:41:15AM -0700, Daniele Di Proietto wrote: >> We only changed the MTU of new internal ports if it is bigger than the >> bridge minimum. But when the minimum MTU of the bridge is updated we >> change the MTU of

Re: [ovs-dev] [PATCH 2/2] ofproto: Always set MTU for new internal ports.

2016-08-30 Thread Ben Pfaff
On Tue, Aug 30, 2016 at 11:41:15AM -0700, Daniele Di Proietto wrote: > We only changed the MTU of new internal ports if it is bigger than the > bridge minimum. But when the minimum MTU of the bridge is updated we > change the MTU of all internal ports no matter what. > > The behavior is

[ovs-dev] [PATCH 2/2] ofproto: Always set MTU for new internal ports.

2016-08-30 Thread Daniele Di Proietto
We only changed the MTU of new internal ports if it is bigger than the bridge minimum. But when the minimum MTU of the bridge is updated we change the MTU of all internal ports no matter what. The behavior is inconsistent, because now the internal ports MTU depends on the order in which the