General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Daniel Sterling <sterling.daniel@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	Michael Richardson <mcr+ietf@sandelman.ca>,
	 bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] openwrt e1000e (was: Re:  cake + ipv6)
Date: Tue, 17 Nov 2020 19:00:05 -0500	[thread overview]
Message-ID: <CAJZMiucR=2sD0YNrh5PbJX4338Zspi1yHh5yxidPNQQFt-BQ1A@mail.gmail.com> (raw)
In-Reply-To: <875z7ujgxe.fsf@toke.dk>

> Daniel Sterling <sterling.daniel@gmail.com> writes:
> In my case: I am happy to report this is *not* a bug or an issue with
> cake, as I originally thought. I am able to reproduce the issue I was

Wanted to give an update on this. All my issues (odd latency, slow
throughput, etc) went away when I switched from the in-kernel e1000e
driver to Intel's NAPI driver.

That is, I compiled e1000e driver 3.8.7-NAPI from
https://sourceforge.net/projects/e1000/files/e1000e%20stable/ ,
instead of using the mainline e1000e driver from kernel 5.4.75 in
openwrt dev.

After switching to the Intel driver, my internet has been rock solid.

My NIC from lspci:
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

This is the "Intel EXPI9301CT Desktop Adapter Gigabit" from newegg. I
bought it figuring it would have good linux support. *grin*

And it does, but not with the mainline driver it seems. The in-kernel
driver doesn't (I assume) support NAPI -- so very possibly this is due
to the NAPI support in the out-of-tree driver (vs being an issue with
the driver itself)

-- Dan

  reply	other threads:[~2020-11-18  0:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18  1:52 [Bloat] cake + ipv6 Daniel Sterling
2020-08-18  2:28 ` Jonathan Morton
2020-08-18  2:54 ` Kenneth Porter
     [not found] ` <D7DF629BCBA6767D1E78A973@172.27.17.193>
2020-08-18  3:44   ` Daniel Sterling
2020-08-18  4:15     ` Jonathan Morton
2020-08-18  6:41       ` Sebastian Moeller
2020-08-18 14:17 ` Y
2020-08-18 21:55 ` Michael Richardson
2020-09-23 17:36   ` Daniel Sterling
2020-09-23 18:13     ` Jonathan Morton
2020-09-24  1:07       ` Daniel Sterling
2020-09-28  6:22         ` Daniel Sterling
2020-09-28 15:14           ` Toke Høiland-Jørgensen
2020-10-01  5:09             ` Daniel Sterling
2020-10-01 11:59               ` Toke Høiland-Jørgensen
2020-11-18  0:00                 ` Daniel Sterling [this message]
2020-11-20 23:25                   ` [Bloat] finally got the proper cake experience (was: Re: openwrt e1000e (was: Re: cake + ipv6)) Daniel Sterling

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='CAJZMiucR=2sD0YNrh5PbJX4338Zspi1yHh5yxidPNQQFt-BQ1A@mail.gmail.com' \
    --to=sterling.daniel@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=mcr+ietf@sandelman.ca \
    --cc=toke@toke.dk \
    /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