Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Witte <m.witte@neusta.de>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Slow e1000e Network Interface with different kernel
Date: Thu, 2 Sep 2021 12:01:08 +0200	[thread overview]
Message-ID: <0c8eb89c-4a55-d977-312f-6856ea5b59ba@neusta.de> (raw)

Scenario: Plugin into network, establishes link and IP is assigned.
scp from another machine in the same subnet gives approx. 1kb/sec.
Cross check with an usb 3 dock with integrated network adapter. Full speed.

Kai Heng-Feng build a patch for tgp https://lkml.org/lkml/2021/7/12/2927
His deb kernel packages with that patch based on 5.10.x kernel ran full 
throttle on this machine.
However this was the only successfull attempt to get full speed.

The Kernel Mainline 5.13. contains visual similar patches, but they 
still have the slow down on the same machine.
Some people suspect pcie changes at that point.

Some curious fact I found out while testing: I booted up a manjaro 
(current) usb stick and had full speed on the e1000e. Then I installed 
manjaro from that stick to the harddrive. Booted that and it didn't 
perform well.

As this is my first rodeo on this mailinglist, I need to reference some 
information:

Referencing: https://bugzilla.kernel.org/show_bug.cgi?id=213377
Here is the launchpad: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927925
e1000e Sourceforge bugreport(s): https://sourceforge.net/p/e1000/bugs/681/
This is still an issue with all current mainline kernels. Last test was 
5.14 RC7

I can provide any output you need.



             reply	other threads:[~2021-09-02 10:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 10:01 Marco Witte [this message]
2021-09-02 10:17 ` [Intel-wired-lan] Slow e1000e Network Interface with different kernel Paul Menzel
2021-09-02 10:28 ` Sasha Neftin

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=0c8eb89c-4a55-d977-312f-6856ea5b59ba@neusta.de \
    --to=m.witte@neusta.de \
    --cc=intel-wired-lan@osuosl.org \
    /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