From: Aaron Wood <woody77@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Intel recommends against LRO in routing and bridging.
Date: Mon, 8 Aug 2016 15:13:53 -0700 [thread overview]
Message-ID: <CALQXh-OH+_sYAY3XvJ48p_s2yHKzr-L5gvEWO3kGMRzKC=eDPQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
Just came across this at the top of the README for the ixgbe driver: (
http://downloadmirror.intel.com/22919/eng/README.txt)
WARNING: The ixgbe driver compiles by default with the LRO (Large Receive
Offload) feature enabled. This option offers the lowest CPU utilization for
receives, but is completely incompatible with *routing/ip forwarding* and
*bridging*. If enabling ip forwarding or bridging is a requirement, it is
necessary to disable LRO using compile time options as noted in the LRO
section later in this document. The result of not disabling LRO when combined
with ip forwarding or bridging can be low throughput or even a kernel panic.
-Aaron
[-- Attachment #2: Type: text/html, Size: 894 bytes --]
next reply other threads:[~2016-08-08 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 22:13 Aaron Wood [this message]
2016-08-10 9:44 ` Dave Täht
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALQXh-OH+_sYAY3XvJ48p_s2yHKzr-L5gvEWO3kGMRzKC=eDPQ@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/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