Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fastpass: A Centralized "Zero-Queue" Datacenter Network
Date: Fri, 18 Jul 2014 16:20:28 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1407181617020.17284@nftneq.ynat.uz> (raw)
In-Reply-To: <CAK-n8j52X=DvAKxnV3gyw8J9N-=0kMLqGtG0Lc1bYtB4mV3Kkw@mail.gmail.com>

On Fri, 18 Jul 2014, Jim Reisert AD1C wrote:

> "Fastpass is a datacenter network framework that aims for high
> utilization with zero queueing. It provides low median and tail
> latencies for packets, high data rates between machines, and flexible
> network resource allocation policies. The key idea in Fastpass is
> fine-grained control over packet transmission times and network
> paths."
>
> Read more at....
>
> http://fastpass.mit.edu/

<sarcasam>
and all it takes is making one central point aware of all the communications 
that is going to take place so that it can coordinate everything.

That is sure to scale to an entire datacenter, and beyond that to the Internet
</sarcasam>

now, back in the real world, you can't reliably get that information for a 
single host, let alone an entire datacenter.

not to mention the scalability issues in trying to get that info to a central 
point so that it can compute the N! possible paths for the data to take, along 
with the data from all the other systems to pack them most efficiently into the 
avilable paths.

Someone may eventually make something useful out of this, but I think that it's 
at best a typical academic ivory tower type of solution.

David Lang

  reply	other threads:[~2014-07-18 23:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 13:48 Jim Reisert AD1C
2014-07-18 23:20 ` David Lang [this message]
2014-07-18 23:27   ` David Lang
2014-07-19  0:23     ` Dave Taht
2014-07-19  0:36       ` Dave Taht
2014-07-19 16:41       ` Valdis.Kletnieks
2014-07-19 17:31         ` Dave Taht
2014-07-19  0:04   ` Valdis.Kletnieks
2014-07-19  0:31     ` David Lang

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1407181617020.17284@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jjreisert@alum.mit.edu \
    /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