General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Nils Andreas Svee <me@lochnair.net>, Dave Taht <dave.taht@gmail.com>
Cc: "Toke Høiland-Jørgensen via Cake" <cake@lists.bufferbloat.net>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>,
	"Simon Sundberg" <Simon.Sundberg@kau.se>
Subject: Re: [Bloat] [Cake] Fwd: [Galene] Dave on bufferbloat and jitter at 8pm CET Tuesday 23
Date: Fri, 26 Feb 2021 12:47:25 +0100	[thread overview]
Message-ID: <87mtvryrsi.fsf@toke.dk> (raw)
In-Reply-To: <86692246-90d3-4b5b-bcb3-5a67a29d67f7@lochnair.net>

Nils Andreas Svee <me@lochnair.net> writes:

> On 2/25/21 11:30 AM, Toke Høiland-Jørgensen wrote:
>
>> Ah, wireguard doesn't have XDP support, so that's likely not going to
>> work; and if you run it on the physical interface, even if you didn't
>> get driver errors, the tool would just see the encrypted packets which
>> is not terribly helpful (it parses TCP timestamps to match
>> incoming/outgoing packets and compute the RTT).
>
> I figured that might be the case. Yes I would've disabled the VPN if I 
> didn't get driver errors.
> I changed the network interface to use an emulated Intel E1000 tonight, 
> and if I bypass the VPN it works as it should.

Right, awesome!

>> I guess we should be more flexible about which hooks we support, so it
>> can also be used on devices with no XDP support. Adding in Simon, who is
>> writing the code; I think he is focused on getting a couple of other
>> features done first, but this could go on the TODO list :)
>
> It's not like I'm in a hurry, and I'd probably need some time to figure 
> out how to tweak the CAKE parameters correctly with this anyway ;)
>
> Speaking of, isn't one of the challenges with solutions like these that 
> it's hard to tell when conditions have improved and allow for more 
> throughput? At least that's what I remember being the issue when I 
> tested CAKE's autorate-ingress back in the day.

Yeah, there would have to be some kind of probing to discover when the
bandwidth goes up (maybe something like what BBR does?). Working out the
details of this is still in the future, this is all just loose plans
that I'll try to get back to once we have the measurement tool working
reasonably well. Input and experiments welcome, of course!

-Toke

  reply	other threads:[~2021-02-26 11:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874ki24ref.wl-jch@irif.fr>
2021-02-23 17:46 ` [Bloat] " Dave Taht
2021-02-23 21:30   ` [Bloat] [Cake] " Nils Andreas Svee
2021-02-24  1:14     ` Dave Taht
2021-02-24  1:29       ` Stephen Hemminger
2021-02-24 10:51       ` Toke Høiland-Jørgensen
2021-02-24 22:49         ` Nils Andreas Svee
2021-02-24 23:27           ` Toke Høiland-Jørgensen
2021-02-24 23:35             ` Nils Andreas Svee
2021-02-25 10:30               ` Toke Høiland-Jørgensen
2021-02-26  0:32                 ` Nils Andreas Svee
2021-02-26 11:47                   ` Toke Høiland-Jørgensen [this message]
2021-02-26 15:27                     ` Nils Andreas Svee
2021-02-26 16:59                       ` Bless, Roland (TM)
2021-02-26 17:14                         ` Sebastian Moeller
2021-02-26 17:50                           ` Bless, Roland (TM)
2021-02-24 15:19     ` Taraldsen Erik
2021-02-24 16:11       ` Toke Høiland-Jørgensen
2021-02-24 18:43       ` [Bloat] [Make-wifi-fast] " Jonathan Morton
2021-02-24 23:27       ` [Bloat] " Nils Andreas Svee
2021-02-25  8:18         ` Taraldsen Erik
2021-02-26  0:19           ` Nils Andreas Svee
2021-02-26  7:26             ` Taraldsen Erik
2021-02-26 12:26               ` Toke Høiland-Jørgensen
2021-02-26 14:25               ` Nils Andreas Svee
2021-02-26 15:08                 ` Taraldsen Erik

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=87mtvryrsi.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=Simon.Sundberg@kau.se \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=me@lochnair.net \
    /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