Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Adrian Popescu <adriannnpopescu@gmail.com>,
	Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] CAKE set-associative hashing
Date: Mon, 30 Oct 2017 00:39:47 +0200	[thread overview]
Message-ID: <CAJq5cE2i9E9gW-aAy5ts5Bkp+UB8Rhu22nEnE2fnLUm8t69whg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5dQUebb-WvW9Xrvhkh4W1CUmNJOKSsFxXX3uY-Pyz4bw@mail.gmail.com>

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

In CPUs, 4-way is now common in first-level caches, 16-way at last-level.
It is a tradeoff between guaranteed hit latency (necessary in synchronous
hardware) and collision rate.  In software, average hit latency is usually
more relevant, and worst-case throughput otherwise.

IMHO, having a separate qdisc tree per hardware queue is the wrong design.
Better would be a single qdisc (or tree thereof) that can be drained
concurrently into all queues.  That currently seems to be easiest to
arrange by putting the qdiscs in userspace, but theoretically that need not
be so.

- Jonathan Morton

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

      reply	other threads:[~2017-10-29 22:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-29 10:07 Adrian Popescu
2017-10-29 10:14 ` Jonathan Morton
2017-10-29 15:38   ` Adrian Popescu
2017-10-29 22:20     ` Dave Taht
2017-10-29 22:39       ` Jonathan Morton [this message]

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=CAJq5cE2i9E9gW-aAy5ts5Bkp+UB8Rhu22nEnE2fnLUm8t69whg@mail.gmail.com \
    --to=chromatix99@gmail.com \
    --cc=adriannnpopescu@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@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