netdev - Re: GSO and IPv4 forwarding

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]

Message-ID: <20101026135250.74870932@nehalam>
Date:	Tue, 26 Oct 2010 13:52:50 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Kevin Wilson <wkevils@...il.com>
Cc:	Eric Dumazet <eric.dumazet@...il.com>, netdev@...r.kernel.org
Subject: Re: GSO and IPv4 forwarding

On Tue, 26 Oct 2010 22:26:07 +0200
Kevin Wilson <wkevils@...il.com> wrote:

> Hi,
> Thanks a lot for your quick answer, I appreciate it (and did not
> expect it to be so quick!)
> 
> Can someone please explain in 2-3 short sentences Why GRO can be
> forwarded and LRO cannot be forwarded ?
> rgs,
> Kevin

LRO merges packets together creating one large skb.  This is a layering
violation for forwarding or bridging (it violates end to end principle).

GRO maintains the headers of each packet and passes them as
a cluster.
--
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