Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] memory
Date: Thu, 29 Oct 2015 12:02:31 +0100	[thread overview]
Message-ID: <87h9laey48.fsf@toke.dk> (raw)
In-Reply-To: <E8C94AA7-6123-45D9-846F-A0F0C791919F@gmx.de> (Sebastian Moeller's message of "Thu, 29 Oct 2015 11:48:01 +0100")

Sebastian Moeller <moeller0@gmx.de> writes:

> Yes, while trying to be funny I glossed over that part a bit (the
> loooong RTTs part was aiming at that), sorry. But really I am wonder
> what it is that makes my position that cake should expose and honor a
> packet limit for its queueing so controversial;

The suggestion in itself is not necessarily controversial. However, the
road to bloated interfaces is covered in good intentions. Each addition
may be worthwhile in itself, but the sum of them becomes a horrible mess
to configure (I'm being a bit hyperbolic here, but I'm sure you get my
gist). So I'd rather say that for each possible configuration variable,
we should figure out if there is a way to avoid exposing it, and only
exposing it if we can't find a way to do that. Rather than going with
the "easy" solution of just making it configurable and leaving the user
to figure it out.

-Toke

  reply	other threads:[~2015-10-29 11:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29  9:01 Dave Taht
2015-10-29  9:56 ` Sebastian Moeller
2015-10-29 10:04   ` Toke Høiland-Jørgensen
2015-10-29 10:11     ` Sebastian Moeller
2015-10-29 10:14       ` Toke Høiland-Jørgensen
2015-10-29 10:48         ` Sebastian Moeller
2015-10-29 11:02           ` Toke Høiland-Jørgensen [this message]
     [not found]             ` <6A01B7A9-BB31-4CF5-BE84-A54A2B860564@gmx.de>
2015-10-29 15:40               ` Toke Høiland-Jørgensen
2015-10-30  9:13                 ` Sebastian Moeller
2015-10-30 12:07                   ` Dave Taht
2015-10-30 12:21                     ` Sebastian Moeller

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=87h9laey48.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cake@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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