From: Eric Dumazet <eric.dumazet@gmail.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: intel-wired-lan@lists.osuosl.org,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Driver has suspect GRO implementation, TCP performance may be compromised.
Date: Tue, 28 May 2019 10:18:59 -0700 [thread overview]
Message-ID: <8627ea1e-8e51-c425-97f6-aeb57176e11a@gmail.com> (raw)
In-Reply-To: <e070e241-fb65-a5b0-3155-7380a9203bcf@molgen.mpg.de>
On 5/28/19 8:42 AM, Paul Menzel wrote:
> Dear Linux folks,
>
>
> Occasionally, Linux outputs the message below on the workstation Dell
> OptiPlex 5040 MT.
>
> TCP: net00: Driver has suspect GRO implementation, TCP performance may be compromised.
>
> Linux 4.14.55 and Linux 5.2-rc2 show the message, and the WWW also
> gives some hits [1][2].
>
> ```
> $ sudo ethtool -i net00
> driver: e1000e
> version: 3.2.6-k
> firmware-version: 0.8-4
> expansion-rom-version:
> bus-info: 0000:00:1f.6
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: no
> ```
>
> Can the driver e1000e be improved?
>
> Any idea, what triggers this, as I do not see it every boot? Download
> of big files?
>
Maybe the driver/NIC can receive frames bigger than MTU, although this would be strange.
diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
index c61edd023b352123e2a77465782e0d32689e96b0..cb0194f66125bcba427e6e7e3cacf0c93040ef61 100644
--- a/net/ipv4/tcp_input.c
+++ b/net/ipv4/tcp_input.c
@@ -150,8 +150,10 @@ static void tcp_gro_dev_warn(struct sock *sk, const struct sk_buff *skb,
rcu_read_lock();
dev = dev_get_by_index_rcu(sock_net(sk), skb->skb_iif);
if (!dev || len >= dev->mtu)
- pr_warn("%s: Driver has suspect GRO implementation, TCP performance may be compromised.\n",
- dev ? dev->name : "Unknown driver");
+ pr_warn("%s: Driver has suspect GRO implementation, TCP performance may be compromised."
+ " len %u mtu %u\n",
+ dev ? dev->name : "Unknown driver",
+ len, dev ? dev->mtu : 0);
rcu_read_unlock();
}
}
next prev parent reply other threads:[~2019-05-28 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 15:42 Paul Menzel
2019-05-28 17:18 ` Eric Dumazet [this message]
2019-05-29 14:49 ` Paul Menzel
2019-05-29 16:00 ` Eric Dumazet
2019-05-29 16:35 ` Stephen Hemminger
2019-05-30 22:52 ` Alexander Duyck
2019-05-30 23:56 ` Eric Dumazet
2019-07-22 16:04 ` Paul Menzel
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=8627ea1e-8e51-c425-97f6-aeb57176e11a@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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
all inboxes | Powered by JetHome®