From: Ben Hutchings <bhutchings@solarflare.com>
To: John Fastabend <john.r.fastabend@intel.com>
Cc: David Miller <davem@davemloft.net>, <netdev@vger.kernel.org>,
Shradha Shah <sshah@solarflare.com>,
Patrick McHardy <kaber@trash.net>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH net] macvlan: Disable LRO on lowerdev; warn if it's turned back on
Date: Tue, 21 Feb 2012 20:28:56 +0000 [thread overview]
Message-ID: <1329856136.2689.46.camel@bwh-desktop> (raw)
In-Reply-To: <4F43F816.6070908@intel.com>
On Tue, 2012-02-21 at 12:01 -0800, John Fastabend wrote:
> On 2/21/2012 11:13 AM, Ben Hutchings wrote:
> > Large Receive Offload (LRO) is only appropriate for packets that are
> > destined for the host, and should be disabled if received packets may
> > be forwarded.
> >
> > Further, macvtap_skb_to_vnet_hdr() will BUG() on a packet received
> > with LRO (but not GRO).
> >
> > Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
> > ---
> > I'm not really familiar with macvlan so I'm not certain that this should
> > be applied to all modes.
> >
> > Ben.
> >
> > drivers/net/macvlan.c | 7 +++++++
> > 1 files changed, 7 insertions(+), 0 deletions(-)
> >
>
> But this patch assumes the macvlan is forwarding traffic to a guest
> via macvtap. Which is an assumption that may not be true.
>
> It seems more appropriate for the macvtap driver to do these checks
> after all its the driver that may BUG() with LRO.
That's what I thought at first, but then I looked through what macvlan
was doing and it certainly appears to re-transmit skbs in all modes.
That's not valid when gso_size != 0 and gso_type == 0.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2012-02-21 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 19:13 [PATCH net] macvlan: Disable LRO on lowerdev; warn if it's turned back on Ben Hutchings
2012-02-21 20:01 ` John Fastabend
2012-02-21 20:28 ` Ben Hutchings [this message]
2012-02-21 21:46 ` Ben Greear
2012-02-25 22:07 ` Eric W. Biederman
2012-02-25 22:49 ` Ben Hutchings
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=1329856136.2689.46.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=john.r.fastabend@intel.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=sshah@solarflare.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.