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: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] aqm bumps on the wire
Date: Tue, 31 Jul 2018 01:21:32 +0300	[thread overview]
Message-ID: <91027520-F63D-4B26-BBF6-07C4364994A6@gmail.com> (raw)
In-Reply-To: <CAA93jw5zCQGMXYC-cN5O75Q78LuR-aWKh=k8DwU-aa72h=3irg@mail.gmail.com>

> On 30 Jul, 2018, at 3:36 am, Dave Taht <dave.taht@gmail.com> wrote:
> 
> http://cseweb.ucsd.edu/~gmporter/papers/netbump-ancs12.pdf

Some notable comments on Linux network-stack latency in here.  However, it appears that they tried only a 2.6.x kernel, got bad results, and promptly gave up.  No investigation of whether a decade-newer 4.x kernel might, just possibly, have incorporated improvements.

 - Jonathan Morton


      reply	other threads:[~2018-07-30 22:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30  0:36 Dave Taht
2018-07-30 22:21 ` 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=91027520-F63D-4B26-BBF6-07C4364994A6@gmail.com \
    --to=chromatix99@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