netdev - Re: [PATCH RFC net-next] vxlan: GRO support at tunnel layer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 30 Jun 2015 07:06:34 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Rick Jones <rick.jones2@...com>
Cc:	Ramu Ramamurthy <sramamur@...ux.vnet.ibm.com>,
	Tom Herbert <tom@...bertland.com>, davem@...emloft.net,
	netdev@...r.kernel.org
Subject: Re: [PATCH RFC net-next] vxlan: GRO support at tunnel layer

On Mon, 2015-06-29 at 13:04 -0700, Rick Jones wrote:

> PS  FWIW, if I shift from using just the linux native vxlan to a "mostly 
> full" set of OpenStack compute node plumbing - two OVS bridges and a 
> linux bridge and associated plumbing with a vxlan tunnel defined in OVS, 
> but nothing above the Linux bridge (and no VMs) I see more like 4.9 
> Gbit/s.  The veth pair connecting the linux bridge to the top ovs bridge 
> show rx checksum and gro enabled.  the linux bridge itself shows GRO but 
> rx checksum off (fixed).  I'm not sure how to go about checking the OVS 
> constructs.
> 

This is exactly why we had to implement GRO at the first stage.

We can not assume a proper netdev tunnel is there where we can use
gro_cells.



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html