From: David Miller <davem@davemloft.net>
To: markryde@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: skb_warn_if_lro(skb) in ip_forward()
Date: Mon, 27 Apr 2009 00:04:13 -0700 (PDT) [thread overview]
Message-ID: <20090427.000413.208482056.davem@davemloft.net> (raw)
In-Reply-To: <dac45060904262343v481d2665s4074e901852406b5@mail.gmail.com>
From: Mark Ryden <markryde@gmail.com>
Date: Mon, 27 Apr 2009 09:43:39 +0300
> Hello,
>
> I would appreciate if somebody will explain in a few sentences, why,
> when forwarding
> a packet in IPV4 , in ip_forward() method, (net/ipv4/ip_forward.c) we
> drop the packet
> if it is lro.
Because we have no means by which to reconstitute the original
sub-frames so that we can forward them properly.
This is why, when forwarding or bridging is enabled on an interface
we disable LRO on all devices involved. Therefore we should never
see LRO frames here.
prev parent reply other threads:[~2009-04-27 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 6:43 skb_warn_if_lro(skb) in ip_forward() Mark Ryden
2009-04-27 6:53 ` Eric Dumazet
2009-04-27 7:04 ` David Miller [this message]
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=20090427.000413.208482056.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=markryde@gmail.com \
--cc=netdev@vger.kernel.org \
/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).