Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Luca Muscariello <luca.muscariello@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
	Cake List <cake@lists.bufferbloat.net>,
	AQM IETF list <aqm@ietf.org>
Subject: Re: [Cake] paper: per flow fairness in a data center network
Date: Thu, 13 Dec 2018 10:51:17 +0100	[thread overview]
Message-ID: <CAHx=1M4QCx7LbxcdnUo-Y0QxCWhUUu2ZqqyZmuMtsWJZ9FNgew@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw58CW6We3NCa=F60yqvCPuvOexpRJQWS6M_k_5WnXUmhw@mail.gmail.com>

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

I disagree on the claims that DC switches do not implement anything.
They do, from quite some time now.

https://www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-series-switches/white-paper-c11-738488.html



On Thu, Dec 6, 2018 at 4:19 AM Dave Taht <dave.taht@gmail.com> wrote:

> While I strongly agree with their premise:
>
> "Multi-tenant DCNs cannot rely on specialized protocols and mechanisms
> that assume single ownership and end-system compliance. It is
> necessary rather to implement general, well-understood mechanisms
> provided as a network service that require as few assumptions about DC
> workload as possible."
>
> ... And there's a solid set of links to current work, and a very
> interesting comparison to pfabric, their DCTCP emulation is too flawed
> to be convincing, and we really should get around to making the ns2
> fq_codel emulation fully match reality. This is also a scenario where
> I'd like to see cake tried, to demonstrate the effectiveness (or not!)
> of 8 way set associative queuing, cobalt, per host/per flow fq, etc,
> vs some of the workloads they outline.
>
> https://perso.telecom-paristech.fr/drossi/paper/rossi18hpsr.pdf
>
> --
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-205-9740
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>

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

  parent reply	other threads:[~2018-12-13  9:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06  3:18 Dave Taht
2018-12-13  7:58 ` dario.rossi
2018-12-13  9:51 ` Luca Muscariello [this message]
2018-12-15 17:09   ` [Cake] [Bloat] " Dave Taht
2018-12-15 17:21     ` Dave Taht

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='CAHx=1M4QCx7LbxcdnUo-Y0QxCWhUUu2ZqqyZmuMtsWJZ9FNgew@mail.gmail.com' \
    --to=luca.muscariello@gmail.com \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --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