org>; Jan Scheurich <jan.scheur...@web.de>
Subject: Re: [ovs-dev] [PATCH v2 14/17] datapath: Fix skb->protocol for vlan
frames
On Thu, Jan 19, 2017 at 03:12:20PM -0800, Joe Stringer wrote:
> On 19 January 2017 at 12:17, Pravin Shelar <pshe...@ovn.org> wrote:
> > On We
On Thu, Jan 19, 2017 at 03:12:20PM -0800, Joe Stringer wrote:
> On 19 January 2017 at 12:17, Pravin Shelar wrote:
> > On Wed, Jan 18, 2017 at 4:53 PM, Yang, Yi wrote:
> >> On Wed, Jan 18, 2017 at 01:29:14PM -0800, Joe Stringer wrote:
> >>> On 18 January 2017
On 19 January 2017 at 12:17, Pravin Shelar wrote:
> On Wed, Jan 18, 2017 at 4:53 PM, Yang, Yi wrote:
>> On Wed, Jan 18, 2017 at 01:29:14PM -0800, Joe Stringer wrote:
>>> On 18 January 2017 at 11:54, Eric Garver wrote:
>>> > On Tue, Jan 17,
On Wed, Jan 18, 2017 at 4:53 PM, Yang, Yi wrote:
> On Wed, Jan 18, 2017 at 01:29:14PM -0800, Joe Stringer wrote:
>> On 18 January 2017 at 11:54, Eric Garver wrote:
>> > On Tue, Jan 17, 2017 at 12:37:19AM +, Yang, Yi Y wrote:
>> >> What userspace do "802.1ad
On Wed, Jan 18, 2017 at 01:29:14PM -0800, Joe Stringer wrote:
> On 18 January 2017 at 11:54, Eric Garver wrote:
> > On Tue, Jan 17, 2017 at 12:37:19AM +, Yang, Yi Y wrote:
> >> What userspace do "802.1ad patches" depend on? Per Pravin's statement, we
> >> just backport 802.1ad
Hi, Eric
We hope Jiri's L3 patchset can be applied into current ovs because we and
Ericsson guys are enabling packet_type support and PTAP & non-PTAP based on L3
patchset, Pravin said you're backporting your 802.1ad patches from net-next to
ovs, we don't know when your patches can be posted in
On Mon, Jan 09, 2017 at 03:03:00PM +0530, Pravin Shelar wrote:
> On Tue, Jan 3, 2017 at 6:47 AM, Yang, Yi Y wrote:
> > Pravin, the issue is current ovs has too many differences from net-next
> > tree, the best way is to apply all the patches before your patch, but it
> >
On Tue, Jan 3, 2017 at 6:47 AM, Yang, Yi Y wrote:
> Pravin, the issue is current ovs has too many differences from net-next tree,
> the best way is to apply all the patches before your patch, but it seems a
> super huge work, it is out of my capability :-) Anybody of you is
Pravin, the issue is current ovs has too many differences from net-next tree,
the best way is to apply all the patches before your patch, but it seems a
super huge work, it is out of my capability :-) Anybody of you is working on
this?
-Original Message-
From: Pravin Shelar
Do not always set skb->protocol to be the ethertype of the L3 header.
For a packet with non-accelerated VLAN tags skb->protocol needs to be the
ethertype of the outermost non-accelerated VLAN ethertype.
Any VLAN offloading is undone on the OVS netlink interface, and any VLAN tags
added by
10 matches
Mail list logo