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: <20110405084655.10937250@nehalam>
Date:	Tue, 5 Apr 2011 08:46:55 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Marc Haber <mh+netdev@...schlus.de>
Cc:	Amit Salecha <amit.salecha@...gic.com>,
	"davem@...emloft.net" <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Ameen Rahman <ameen.rahman@...gic.com>,
	Rajesh Borundia <rajesh.borundia@...gic.com>
Subject: Re: Netxen packet loss with VLANs and LRO (was: [PATCH] netxen: fix
 LRO disable warning)

On Tue, 5 Apr 2011 17:18:54 +0200
Marc Haber <mh+netdev@...schlus.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.
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ