From: Pete Heist <pete@heistp.net>
To: Georgios Amanakis <gamanakis@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Upstream submission of dual-mode fairness patch
Date: Fri, 1 Mar 2019 17:43:18 +0100 [thread overview]
Message-ID: <DD8A7FDE-363D-4C4B-AE9E-FC00DA55376F@heistp.net> (raw)
In-Reply-To: <CACvFP_jUQgosvTARfH8Rrwh-q65tiEwcHeoR1U+hHZw486r_vQ@mail.gmail.com>
> On Mar 1, 2019, at 3:40 PM, Georgios Amanakis <gamanakis@gmail.com> wrote:
>
> Thanks for testing Pete! The unfairness you see occurs if you shape
> ingress using ifb on the same interface you shape egress, right?
> Sounds puzzling to me, and I don't have an explanation right now.
Yes, same interface, so it’s:
apu2a eth0 <—> apu1a eth0 / apu1a eth0.3300 <—> apu2b eth0.3300
Of course, the VLAN interfaces have 4 bytes of extra overhead, which should be accounted for by ether-vlan.
It’s possible there’s some quirkiness here with apu1a, which has a Realtek Ethernet interface with the r8169 driver. With this driver, I find that setting rx-vlan-offload off (ethtool -K eth0 rxvlan off) doubles routed throughput when one-armed routing. That probably shouldn’t be. Nevertheless, the same thing happens with or without that offload enabled.
Or it’s just something in this old kernel again. If I ever have a rig like this with a newer kernel I’ll try it.
next prev parent reply other threads:[~2019-03-01 16:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1788.1551352661.3538.cake@lists.bufferbloat.net>
2019-03-01 10:52 ` Pete Heist
2019-03-01 11:01 ` Toke Høiland-Jørgensen
2019-03-01 11:55 ` Pete Heist
2019-03-01 14:40 ` Georgios Amanakis
2019-03-01 16:43 ` Pete Heist [this message]
2019-03-02 3:02 ` George Amanakis
2019-03-02 4:47 ` George Amanakis
2019-03-02 10:20 ` Pete Heist
2019-03-03 7:19 ` Pete Heist
2019-03-03 9:53 ` Sebastian Moeller
2019-03-03 9:58 ` Jonathan Morton
2019-03-03 11:26 ` Sebastian Moeller
2019-03-03 12:13 ` Jonathan Morton
2019-03-03 12:53 ` Sebastian Moeller
2019-03-03 16:07 ` Pete Heist
2019-03-03 16:10 ` Jonathan Morton
2019-03-03 16:35 ` Pete Heist
2019-03-03 16:40 ` Jonathan Morton
2019-03-03 18:48 ` Pete Heist
2019-03-03 19:03 ` gamanakis
2019-03-03 19:49 ` Pete Heist
2019-03-04 2:55 ` Georgios Amanakis
2019-03-04 3:17 ` Jonathan Morton
2019-03-04 4:22 ` Ryan Mounce
2019-03-04 8:27 ` Pete Heist
2019-03-04 13:17 ` Pete Heist
2019-03-04 14:36 ` Georgios Amanakis
2019-03-03 12:06 ` Pete Heist
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DD8A7FDE-363D-4C4B-AE9E-FC00DA55376F@heistp.net \
--to=pete@heistp.net \
--cc=cake@lists.bufferbloat.net \
--cc=gamanakis@gmail.com \
--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