Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Michel Blais <michel@targointernet.com>, 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 12:54:25 -0700	[thread overview]
Message-ID: <20180611125425.792d4dcc@xeon-e3> (raw)
In-Reply-To: <87wov5hzvq.fsf@toke.dk>

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

  reply	other threads:[~2018-06-11 19:54 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 [this message]
2018-06-11 20:17     ` Dave Taht
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=20180611125425.792d4dcc@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=cake@lists.bufferbloat.net \
    --cc=michel@targointernet.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