mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Regressions <regressions@lists.linux.dev>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Linux Intel LAN Drivers <intel-wired-lan@lists.osuosl.org>,
	Linux Networking <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Fwd: e1000e - slow receive / rx - i219-LM (Alder Lake)
Date: Wed, 10 May 2023 11:49:49 +0700	[thread overview]
Message-ID: <acf162e6-3dc2-6976-bceb-fa82b5e7b2c2@gmail.com> (raw)

Hi,

I noticed a regression report on bugzilla [1]. As many developers don't
take a look on it, I decided to forward it by email. To reach the
reporter, though, you need to log in to bugzilla.

Quoting from the report:
>  Scott Silverman 2023-03-03 17:55:10 UTC > When running kernels 5.15 and newer, poor rx speeds are observed on Alder Lake i219-LM (8086:1A1C) on a Dell Precision 3260 Compact.
> 
> To Reproduce:
> Using iperf3 from the system under test:
> `iperf3 -c <server on local LAN> -R`
> 
> Under kernels 5.7-5.14 (inclusive) performance is near line rate, ~990 Mbps.
> From kernels 5.15 through 6.2 performance is approximately 10-20 Mbps.
> 
> Also of note, the issue doesn't present with servers over the internet (i.e. higher latency links). Over a link with a latency of approximately 20ms I was able to achieve about 600Mbps.
> 
> Interesting workaround, on affected kernels (5.15+) I am able to resolve the issue if an additional device is installed into the systems PCIe slot (tested with an Intel i210 NIC (not connected to LAN) and an Nvidia Quadro P620 GPU).

See bugzilla for details.

To the reporter: It had been great if you also test the latest mainline
(6.4-rc1) to see if this regression has been already fixed.

Anyway, I'm adding this to regzbot:

#regzbot introduced: v5.14..v5.15 https://bugzilla.kernel.org/show_bug.cgi?id=217120
#regzbot title: e1000e performance drop (slow receive/rx) on i219-LM (Alder Lake)

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217120

-- 
An old man doll... just what I always wanted! - Clara

                 reply	other threads:[~2023-05-10  4:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=acf162e6-3dc2-6976-bceb-fa82b5e7b2c2@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=regressions@lists.linux.dev \
    /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®