netdev - RE: curent state of GSO over IPv6 tunnel

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1410776995.7106.143.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Mon, 15 Sep 2014 03:29:55 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Yuval Mintz <Yuval.Mintz@...gic.com>
Cc:	netdev <netdev@...r.kernel.org>
Subject: RE: curent state of GSO over IPv6 tunnel

On Mon, 2014-09-15 at 10:19 +0000, Yuval Mintz wrote:
> > > Hi,
> > >
> > > Tried running simple scenarios using ipv6/ipv6 via gre-tunnel [ip6_gre].
> > >
> > > When I've tried sniffing Tx traffic [tcpdump] I've noticed there were
> > > no aggregations being set, i.e., only MTU-sized packets reached NIC.
> > >
> > > Looking at output of `ethtool -k', I can see `tx_gre_segmentation' is on.
> > >
> > > What's the current state of the feature? Is it feasible and I'm
> > > missing some configuration, or is it yet an unsupported feature?
> > 
> > As far as I know, only bnx2x driver currently supports NETIF_F_GSO_GRE
> > 
> 
> Hi Eric,
> 
> Might be true, but should this flag hold any sway over IPv6?
> [Both at the moment and in general, i.e., if it does not would we need
> an additional feature or simply extend the functionality so that it would
> effect IPv6 as well?]

Both ipv4 and ipv6 are supported under this single flag.

Really, in 2014 all NIC supporting TSO for GRE should support IPv6 as
well.



--
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