From: Stephen Hemminger <shemminger@vyatta.com>
To: Kevin Wilson <wkevils@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>, netdev@vger.kernel.org
Subject: Re: GSO and IPv4 forwarding
Date: Tue, 26 Oct 2010 13:52:50 -0700 [thread overview]
Message-ID: <20101026135250.74870932@nehalam> (raw)
In-Reply-To: <AANLkTik+s4CHgPuY6uhe-0aD=WJs=UHhoEdok4AyTdYJ@mail.gmail.com>
On Tue, 26 Oct 2010 22:26:07 +0200
Kevin Wilson <wkevils@gmail.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.
next prev parent reply other threads:[~2010-10-26 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 20:02 GSO and IPv4 forwarding Kevin Wilson
2010-10-26 20:15 ` Eric Dumazet
2010-10-26 20:26 ` Kevin Wilson
2010-10-26 20:43 ` Eric Dumazet
2010-10-26 20:52 ` Stephen Hemminger [this message]
2010-10-26 20:19 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101026135250.74870932@nehalam \
--to=shemminger@vyatta.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=wkevils@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).