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
| ||
|
Message-ID: <B5657A6538887040AD3A81F1008BEC63BE78AC@avmb3.qlogic.org> Date: Thu, 5 Feb 2015 16:13:36 +0000 From: Yuval Mintz <Yuval.Mintz@...gic.com> To: Eren Türkay <erent@...atlas.com> CC: netdev <netdev@...r.kernel.org>, Eric Dumazet <eric.dumazet@...il.com> Subject: RE: PROBLEM: Bnx2x Checksum/Length Error Over GRE Tunnel > I am not sure if tx offloading will affect the VM performance. Regardless of OVS > problem, there seems to be a bug with segmentation offloading as it's only > possible to use the interface with "tx off". I have compiled the kernel with > debugging on and I can enable debugging on related parts in the kernel for > further information. > > > Here I easily reach line rate with a single flow. > > > > ip tunnel add gre1 mode gre remote 10.246.11.52 local 10.246.11.51 ip > > link set gre1 up ip addr add 7.7.8.51/24 dev gre1 > > ip tunnel add gre1 mode gre remote 10.20.0.162 local 10.20.0.161 ip l set gre1 > up ip addr add 7.7.8.161/24 dev gre1 Tried this on latest net-next [using iproute2] and I didn't manage to hit the issue you've indicated. I.e., traffic seemed to work fine on gre tunnels using both mtu sizes and regardless of whether Tx-checksum-offload was enabled or disabled. Is there anything else which is worth mentioning in your setup? Thanks, Yuval
Powered by blists - more mailing lists