[Bloat] paper: per flow fairness in a data center network

[dario.rossi]

Ciao Dave (&all)
While I'd love to do a bit more on the topic, I recently joined Huawei, and while I still work on networking,  this one is not so aligned with my current set of activities... 
so I cannot unfortunately help moving forward :/
Best,D.
PS fyi Also I tend to read this email less freqiently than @huawei
Sent from my new-but-still-not-so-smart-phone. Excuse my typos and its random fixes
Oo   Chair holder NewNet at Paris  >    Professor, Telecom ParisTech~     Professor, Ecole Polytechnique 

-------- Original message --------From: Dave Taht <dave.taht at gmail.com> Date: 12/6/18  04:18  (GMT+01:00) To: bloat <bloat at lists.bufferbloat.net>, Cake List <cake at lists.bufferbloat.net>, aqm at ietf.org Subject: paper: per flow fairness in a data center network 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/bloat/attachments/20181213/242353d9/attachment-0002.html>