Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Bandwidith rate by host instead of global while using [dual-]srchost and [dual-]dsthost
Date: Mon, 11 Jun 2018 13:17:19 -0700	[thread overview]
Message-ID: <CAA93jw6UXES4UH_99NLX5VFXCL3P7_8_1ew0WKRgqB7rzPUwLw@mail.gmail.com> (raw)
In-Reply-To: <20180611125425.792d4dcc@xeon-e3>

On Mon, Jun 11, 2018 at 12:54 PM, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> On Mon, 11 Jun 2018 21:44:25 +0200
> Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>> Michel Blais <michel@targointernet.com> writes:
>>
>> > Hi all,
>> >
>> > Is it possible while using srchost, or dual-srchost, and dsthost, or
>> > dual-dsthost, to do a bandwidth limitation by host instead of global ? From
>> > what I read, seem like not.
>>
>> No, not currently (as Dave said). I do believe it would be possible to
>> extend the current architecture to support this, though. Basically,
>> making the number of tins configurable to an arbitrary number and making
>> it possible to set individual bandwidths on them should do the trick. A
>> TC filter could then be used to assign traffic to the right tin based on
>> whatever information is available.
>>
>> However, I don't think the current way of finding the next tin to
>> service is going to scale to an arbitrary number of tins, so this
>> probably needs to be changed before such a configuration is really
>> feasible...
>>
>> -Toke
>
> Making cake into a version of HTB is not necessarily a good idea

Not the plan. But arguably, we'd need a list of requirements from a
major head-end
vendor or DPI co (like sandvine) to even try to address the ISP side
of the universe.

I long ago ran out of motivation and money to continue working on
bufferbloat. It's fixed enough,
for those that care. It's on enough devices (more every day) now to
give those that succeed some market advantage.

Heaving cake over the transom is the "last" thing. And after 18
versions in the last round, toke's fried, I'm fried, everybody's
fried. I'm very happy it started cracking 40gbits, stumped at the bug
stopping us.

I do long for the day where I could buy a cable modem, dsl device, can
bus, ont, gpon, wireless router, enode-b, etc, etc off the shelf,
clearly  marketed with bufferbloat-related fixes - and ISPs will
supply default gear that worked "right", etc, etc that all did the
right thing... but I figure that's going to take explicit market
demand, regulation, or a miracle - or all three. And a decade. Or
more.

I *am* going to washington DC week after next for the lanman2018
presentation of cake, and perhaps I'll find a way to raise some hell
with the FCC, congress, or the FTC (suggestions wanted), but...




-- 

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

  reply	other threads:[~2018-06-11 20:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11 15:43 Michel Blais
2018-06-11 17:44 ` Dave Taht
2018-06-11 19:44 ` Toke Høiland-Jørgensen
2018-06-11 19:54   ` Stephen Hemminger
2018-06-11 20:17     ` Dave Taht [this message]
2018-06-12  6:55       ` Pete Heist
2018-06-12 18:55         ` Dave Taht
2018-06-16 15:33           ` Michel Blais
2018-06-16 19:20             ` Pete Heist
2018-06-16 19:26               ` Pete Heist
2018-06-17 13:35             ` Toke Høiland-Jørgensen

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=CAA93jw6UXES4UH_99NLX5VFXCL3P7_8_1ew0WKRgqB7rzPUwLw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=stephen@networkplumber.org \
    --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