Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] best way at getting at tcp ack data?
Date: Sun, 1 Oct 2017 19:40:18 -0700	[thread overview]
Message-ID: <CAA93jw4eY8G7RuBAqH0Dxzryy4SXwNnf6a+ecBgyuTjLD5a60A@mail.gmail.com> (raw)
In-Reply-To: <CAJq5cE1LJJYE+BeoqiCa5rgUpKM1cfNX8RbRwh_Pxy_xmY6MEw@mail.gmail.com>

The crux of my question was what would be the best way to incorporate
the FLOW_DISSECTOR_KEY_TCP into cake whilst retaining all the other
DPI. I would add a "ack_filter" parameter to the rate_flags?

On Sun, Oct 1, 2017 at 6:08 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
> Ah, so effectively you want to drop acks more aggressively than data packets
> when they become a saturating flow in themselves,

Well, no, what I envisioned would try to comprehensively "do the right
thing" when it came to dropping acks, and not actually wait til they
were saturating.

you have a good point though.

Where I see the most use for it is on very slow DSL, and on wifi
(where you have a small packet limit and reliable transfers).

I also don't know what will happen with extensive filtering in place
to the reverse path, reason tells me that the sparse packet priority
scheme when applied to filtered out acks will result in really bursty
throughput on the other side, and it would be better to defer a full
round between deliveries than leave the sparse packet priority scheme
in place, when doing ack filtering. But that's "reason", and that
fails me a lot whilst thinking about queues.

As I believe at least some level of ack filtering is widely
deployed... til now, I've largely been satisfied that the DRR would
deliver a ton of acks that would be filtered out by the device doing
it.

>but without disturbing the
> cues that TCP relies on.  There is some logic behind that, since COBALT
> ramps up quite slowly with very small packets like acks.
>
> I think it's worth opening an issue to remind me to look into that.

Well, I might gather enough gumption to go after it, as well as try
and produce a cleaned up cake branch suitable for inclusion in 4.15.

At the moment I'm starting to prototype a bit with a bfifo, and
perhaps netem, 'cause grokking cake makes my head hurt.

> I still
> don't have a replacement for my MBP, which is complicating matters here.

MBP?

> - Jonathan Morton



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  reply	other threads:[~2017-10-02  2:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01  3:10 Dave Taht
2017-10-01  5:22 ` Jonathan Morton
2017-10-01  5:25   ` Dave Taht
2017-10-02  1:08     ` Jonathan Morton
2017-10-02  2:40       ` Dave Taht [this message]
2017-10-04  3:17         ` Noah Causin
2017-10-04  3:22           ` Jonathan Morton
2017-10-04  3:23           ` Jonathan Morton

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=CAA93jw4eY8G7RuBAqH0Dxzryy4SXwNnf6a+ecBgyuTjLD5a60A@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    /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