On Mon, Dec 8, 2014 at 7:33 AM, Jesse Gross wrote:
> If you look at the implementation of GRO/TSO, I think you will see
> that it does in fact faithfully reconstruct the original message and
> path MTU discovery is preserved. On Linux systems, GRO is enabled by
> default for all workloads - inclu
On Sat, Dec 6, 2014 at 2:47 PM, Nicholas Bastin wrote:
> On Fri, Dec 5, 2014 at 4:51 PM, Jesse Gross wrote:
>>
>> I don't think there is anything inherently wrong with aggregating TCP
>> segments in VXLAN that are not destined for the local host. This is
>> conceptually the same as doing aggregat
On Fri, Dec 5, 2014 at 4:51 PM, Jesse Gross wrote:
> I don't think there is anything inherently wrong with aggregating TCP
> segments in VXLAN that are not destined for the local host. This is
> conceptually the same as doing aggregation for TCP packets where we
> only perform L2 bridging - in th
On Wed, Dec 3, 2014 at 5:45 PM, Jay Vosburgh wrote:
>
> Jay Vosburgh wrote:
>
>> I am able to reproduce a kernel panic on an system using
>>openvswitch when receiving VXLAN traffic under a very specific set of
>>circumstances. This occurs with a recent net-next as well as an Ubuntu
>>3.13
Jay Vosburgh wrote:
> I am able to reproduce a kernel panic on an system using
>openvswitch when receiving VXLAN traffic under a very specific set of
>circumstances. This occurs with a recent net-next as well as an Ubuntu
>3.13 kernel. I'm not sure if the error lies in OVS, GRO, or elsew
Pravin Shelar wrote:
>On Fri, Nov 7, 2014 at 2:29 PM, Jesse Gross wrote:
>> On Fri, Nov 7, 2014 at 1:13 PM, Jay Vosburgh
>> wrote:
>>> Jesse Gross wrote:
>>>
On Fri, Nov 7, 2014 at 10:34 AM, Jesse Gross wrote:
> On Fri, Nov 7, 2014 at 9:40 AM, Pravin Shelar wrote:
>> On Thu, Nov
On Fri, Nov 7, 2014 at 2:29 PM, Jesse Gross wrote:
> On Fri, Nov 7, 2014 at 1:13 PM, Jay Vosburgh
> wrote:
>> Jesse Gross wrote:
>>
>>>On Fri, Nov 7, 2014 at 10:34 AM, Jesse Gross wrote:
On Fri, Nov 7, 2014 at 9:40 AM, Pravin Shelar wrote:
> On Thu, Nov 6, 2014 at 5:58 PM, Jay Vosbur
On Fri, Nov 7, 2014 at 1:13 PM, Jay Vosburgh wrote:
> Jesse Gross wrote:
>
>>On Fri, Nov 7, 2014 at 10:34 AM, Jesse Gross wrote:
>>> On Fri, Nov 7, 2014 at 9:40 AM, Pravin Shelar wrote:
On Thu, Nov 6, 2014 at 5:58 PM, Jay Vosburgh
wrote:
> [...]
> I'm not sure if this is
Jesse Gross wrote:
>On Fri, Nov 7, 2014 at 10:34 AM, Jesse Gross wrote:
>> On Fri, Nov 7, 2014 at 9:40 AM, Pravin Shelar wrote:
>>> On Thu, Nov 6, 2014 at 5:58 PM, Jay Vosburgh
>>> wrote:
[...]
I'm not sure if this is an error on the part of the RX / GRO
processing in assemb
On Fri, Nov 7, 2014 at 10:34 AM, Jesse Gross wrote:
> On Fri, Nov 7, 2014 at 9:40 AM, Pravin Shelar wrote:
>> On Thu, Nov 6, 2014 at 5:58 PM, Jay Vosburgh
>> wrote:
>>>
>>> I am able to reproduce a kernel panic on an system using
>>> openvswitch when receiving VXLAN traffic under a very
On Fri, Nov 7, 2014 at 9:40 AM, Pravin Shelar wrote:
> On Thu, Nov 6, 2014 at 5:58 PM, Jay Vosburgh
> wrote:
>>
>> I am able to reproduce a kernel panic on an system using
>> openvswitch when receiving VXLAN traffic under a very specific set of
>> circumstances. This occurs with a recen
On Thu, Nov 6, 2014 at 5:58 PM, Jay Vosburgh wrote:
>
> I am able to reproduce a kernel panic on an system using
> openvswitch when receiving VXLAN traffic under a very specific set of
> circumstances. This occurs with a recent net-next as well as an Ubuntu
> 3.13 kernel. I'm not sure if
I am able to reproduce a kernel panic on an system using
openvswitch when receiving VXLAN traffic under a very specific set of
circumstances. This occurs with a recent net-next as well as an Ubuntu
3.13 kernel. I'm not sure if the error lies in OVS, GRO, or elsewhere.
In summary
13 matches
Mail list logo
