Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] flow isolation for ISPs
Date: Sat, 8 Apr 2017 08:16:20 +0200	[thread overview]
Message-ID: <266B2248-CDD0-47C2-99CD-C735F731616A@gmail.com> (raw)
In-Reply-To: <B9B9374D-4679-46D4-A2FA-301B4370A694@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 834 bytes --]


>> On Apr 7, 2017, at 10:28 AM, Jonathan Morton <chromatix99@gmail.com <mailto:chromatix99@gmail.com>> wrote:
>>> 
>>> On 7 Apr, 2017, at 11:13, Pete Heist <peteheist@gmail.com <mailto:peteheist@gmail.com>> wrote:
>>> 
>>> One more thought, would it be possible for Cake to optionally include the packet’s mark in the hash?
>> 
>> However, it would be possible to use the “mark” directly as one of the host identifiers which triple-isolate operates on to provide that layer of fairness.  That’s probably what you meant.

Ok, I’m starting to understand in cake_hash how triple-isolate is done. I had some misconceptions, and this is the first time I’ve seen a set-associative hash. In case there's time, I’ll see if I can get the mark idea working. It's probably something useful for only a minority of users...

[-- Attachment #2: Type: text/html, Size: 2522 bytes --]

  parent reply	other threads:[~2017-04-08  6:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  8:27 Pete Heist
2017-04-06  8:39 ` David Lang
2017-04-06  8:48   ` Pete Heist
2017-04-06  8:57 ` Jonathan Morton
2017-04-06  9:04   ` Pete Heist
2017-04-06 10:26   ` Andy Furniss
2017-04-06  9:11 ` Jonathan Morton
2017-04-06  9:26   ` Pete Heist
2017-04-07  8:13     ` Pete Heist
2017-04-07  8:28       ` Jonathan Morton
2017-04-07  9:37         ` Pete Heist
2017-04-07 11:13           ` Sebastian Moeller
2017-04-07 11:42             ` Pete Heist
2017-04-08  6:16           ` Pete Heist [this message]
2017-04-07 10:56         ` John Sager
2017-04-06  9:33 ` Toke Høiland-Jørgensen
2017-04-06 10:26   ` Pete Heist
2017-04-06 10:50     ` Toke Høiland-Jørgensen
2017-04-06 11:34       ` Pete Heist
2017-04-06 12:14         ` Toke Høiland-Jørgensen
2017-04-06 13:30           ` Pete Heist
2017-04-06 13:42             ` Toke Høiland-Jørgensen
2017-04-06 13:50               ` Pete Heist
2017-04-06 14:41               ` Dave Taht
2017-04-06 12:48     ` Andy Furniss
2017-04-06 13:19 Konstantin Shalygin
     [not found] <mailman.340.1491486631.3609.cake@lists.bufferbloat.net>
2017-04-06 14:18 ` Pete Heist
2017-04-06 15:41   ` Andy Furniss

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=266B2248-CDD0-47C2-99CD-C735F731616A@gmail.com \
    --to=peteheist@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