On Tue, Sep 26, 2017 at 4:33 PM, Or Gerlitz wrote:
> On Tue, Sep 26, 2017 at 6:11 PM, John Hurley
> wrote:
>> On Tue, Sep 26, 2017 at 3:12 PM, Or Gerlitz wrote:
>>> On Tue, Sep 26, 2017 at 4:58 PM, John Hurley
On Tue, Sep 26, 2017 at 6:11 PM, John Hurley wrote:
> On Tue, Sep 26, 2017 at 3:12 PM, Or Gerlitz wrote:
>> On Tue, Sep 26, 2017 at 4:58 PM, John Hurley
>> wrote:
>>> On Mon, Sep 25, 2017 at 7:35 PM, Or Gerlitz
On Tue, Sep 26, 2017 at 3:12 PM, Or Gerlitz wrote:
> On Tue, Sep 26, 2017 at 4:58 PM, John Hurley
> wrote:
>> On Mon, Sep 25, 2017 at 7:35 PM, Or Gerlitz wrote:
>>> On Mon, Sep 25, 2017 at 1:23 PM, Simon Horman
>>>
On Tue, Sep 26, 2017 at 4:58 PM, John Hurley wrote:
> On Mon, Sep 25, 2017 at 7:35 PM, Or Gerlitz wrote:
>> On Mon, Sep 25, 2017 at 1:23 PM, Simon Horman
>> wrote:
>>> From: John Hurley
>>>
On Mon, Sep 25, 2017 at 7:35 PM, Or Gerlitz wrote:
> On Mon, Sep 25, 2017 at 1:23 PM, Simon Horman
> wrote:
>> From: John Hurley
>>
>> Compile ovs-tc flower vxlan metadata match fields for offloading. Only
>
> anything
On Mon, Sep 25, 2017 at 1:23 PM, Simon Horman
wrote:
> From: John Hurley
>
> Compile ovs-tc flower vxlan metadata match fields for offloading. Only
anything in the npf kernel bits has direct relation to ovs? what?
> +++
From: John Hurley
Compile ovs-tc flower vxlan metadata match fields for offloading. Only
support offload of tunnel data when the VXLAN port specifically matches
well known port 4789.
Signed-off-by: John Hurley
Signed-off-by: Simon Horman