From: Dave Taht <dave@taht.net>
To: Luca Muscariello <luca.muscariello@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
Cake List <cake@lists.bufferbloat.net>,
AQM IETF list <aqm@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cake] paper: per flow fairness in a data center network
Date: Sat, 15 Dec 2018 09:09:36 -0800 [thread overview]
Message-ID: <87sgyyg1in.fsf@taht.net> (raw)
In-Reply-To: <CAHx=1M4QCx7LbxcdnUo-Y0QxCWhUUu2ZqqyZmuMtsWJZ9FNgew@mail.gmail.com> (Luca Muscariello's message of "Thu, 13 Dec 2018 10:51:17 +0100")
Luca Muscariello <luca.muscariello@gmail.com> writes:
> 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
I'm really impressed. I'd have probably heard about it if they'd
mentioned bufferbloat once :/.
The graphs comparing their performance to arista's are far, far, far too
small to read. You can certainly see a huge improvement on mice in this
paper.
is there a better copy of this paper around?
What's the cheapest form of this switch I can buy? (or beg, borrow, or
steal?) I do need a 10GigE-40GigE capable switch in the lab, and BOY oh
boy oh boy would I love to test this one.
Has this tech made it into their routing products?
>
> 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
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2018-12-15 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 3:18 [Bloat] " Dave Taht
2018-12-13 7:58 ` dario.rossi
2018-12-13 9:51 ` [Bloat] [Cake] " Luca Muscariello
2018-12-15 17:09 ` Dave Taht [this message]
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgyyg1in.fsf@taht.net \
--to=dave@taht.net \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=luca.muscariello@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