From: Stephen Hemminger <shemminger@vyatta.com>
To: Marc Haber <mh+netdev@zugschlus.de>
Cc: Amit Salecha <amit.salecha@qlogic.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Ameen Rahman <ameen.rahman@qlogic.com>,
Rajesh Borundia <rajesh.borundia@qlogic.com>
Subject: Re: Netxen packet loss with VLANs and LRO (was: [PATCH] netxen: fix LRO disable warning)
Date: Tue, 5 Apr 2011 08:46:55 -0700 [thread overview]
Message-ID: <20110405084655.10937250@nehalam> (raw)
In-Reply-To: <20110405151854.GA32759@torres.zugschlus.de>
On Tue, 5 Apr 2011 17:18:54 +0200
Marc Haber <mh+netdev@zugschlus.de> wrote:
> On Tue, Apr 05, 2011 at 08:15:16AM -0500, Amit Salecha wrote:
> > This will fix LRO configuration problem. Do you see packet loss with
> > LRO disable ?
>
> No, with LRO disabled things seem to be fine. LRO gets enabled by
> default though.
LRO and routing are fundamentally incompatible, that is why
the kernel attempts to turn it off. When forwarding packets
should not be combined (end-to-end principle) and that is what
LRO does.
Therefore if doing anything like bridging or forwarding kernel
attempts to get driver to turn LRO off.
prev parent reply other threads:[~2011-04-05 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 10:37 [PATCH] netxen: fix LRO disable warning Amit Kumar Salecha
2011-03-21 10:47 ` Eric Dumazet
2011-03-21 11:13 ` Amit Salecha
2011-03-28 1:08 ` David Miller
2011-03-28 5:33 ` Amit Salecha
2011-03-28 5:17 ` Stanislaw Gruszka
2011-03-28 6:31 ` David Miller
2011-03-28 6:29 ` David Miller
2011-04-03 19:05 ` Netxen packet loss with VLANs and LRO (was: [PATCH] netxen: fix LRO disable warning) Marc Haber
2011-04-05 5:38 ` Amit Salecha
2011-04-05 10:38 ` Michał Mirosław
2011-04-05 12:41 ` Marc Haber
2011-04-05 13:15 ` Amit Salecha
2011-04-05 15:18 ` Marc Haber
2011-04-05 15:46 ` Stephen Hemminger [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=20110405084655.10937250@nehalam \
--to=shemminger@vyatta.com \
--cc=ameen.rahman@qlogic.com \
--cc=amit.salecha@qlogic.com \
--cc=davem@davemloft.net \
--cc=mh+netdev@zugschlus.de \
--cc=netdev@vger.kernel.org \
--cc=rajesh.borundia@qlogic.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