Re: [openstack-dev] [TripleO][Neutron] PMTUd broken in gre networks

2014-01-23 Thread Robert Collins
I'll set some time aside next week to drill into that. I certainly don't recall seeing any utilization issues when I was first troubleshooting. On 24 January 2014 07:26, Salvatore Orlando wrote: > Hi, > > My expertise on the subject is pretty much zero, but the performance loss > (which I think i

Re: [openstack-dev] [TripleO][Neutron] PMTUd broken in gre networks

2014-01-23 Thread Salvatore Orlando
Hi, My expertise on the subject is pretty much zero, but the performance loss (which I think is throughput loss) is so blatant that perhaps there's more than the MTU issue. From what Robert writes, GRO definitely plays a role too. My only suggestion would be to route the question to ovs-discuss i

Re: [openstack-dev] [TripleO][Neutron] PMTUd broken in gre networks

2014-01-22 Thread Rick Jones
On 01/22/2014 03:01 AM, Robert Collins wrote: I certainly think having the MTU set to the right value is important. I wonder if there's a standard way we can signal the MTU (e.g. in the virtio interface) other than DHCP. Not because DHCP is bad, but because that would work with statically injecte

Re: [openstack-dev] [TripleO][Neutron] PMTUd broken in gre networks

2014-01-22 Thread Ian Wells
On 22 January 2014 12:01, Robert Collins wrote: > > Getting the MTU *right* on all hosts seems to be key to keeping your hair > > attached to your head for a little longer. Hence the DHCP suggestion to > set > > it to the right value. > > I certainly think having the MTU set to the right value i

Re: [openstack-dev] [TripleO][Neutron] PMTUd broken in gre networks

2014-01-22 Thread Robert Collins
On 22 January 2014 21:28, Ian Wells wrote: > On 22 January 2014 00:00, Robert Collins wrote: >> >> I think dropping frames that can't be forwarded is entirely sane - at >> >> a guess it's what a physical ethernet switch would do if you try to >> send a 1600 byte frame (on a non-jumbo-frame switch

Re: [openstack-dev] [TripleO][Neutron] PMTUd broken in gre networks

2014-01-22 Thread Ian Wells
On 22 January 2014 00:00, Robert Collins wrote: > I think dropping frames that can't be forwarded is entirely sane - at > a guess it's what a physical ethernet switch would do if you try to > send a 1600 byte frame (on a non-jumbo-frame switched network) - but > perhaps there is an actual standar

Re: [openstack-dev] [TripleO][Neutron] PMTUd broken in gre networks

2014-01-21 Thread Robert Collins
On 22 January 2014 10:01, Ian Wells wrote: > On 21 January 2014 21:23, Robert Collins wrote: >> >> In OpenStack we've got documentation[1] that advises setting a low MTU >> for tenants to workaround this issue (but the issue itself is >> unsolved) - this is a problem because PMTU is fairly import

Re: [openstack-dev] [TripleO][Neutron] PMTUd broken in gre networks

2014-01-21 Thread Ian Wells
On 21 January 2014 21:23, Robert Collins wrote: > In OpenStack we've got documentation[1] that advises setting a low MTU > for tenants to workaround this issue (but the issue itself is > unsolved) - this is a problem because PMTU is fairly important :) > Lowering *every* tenant when one tenant so