From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] barbarians at the gateways
Date: Tue, 22 Oct 2013 00:31:33 +0200 [thread overview]
Message-ID: <2hfxas9kmlfvv3r80gjjsqgk.1382394693673@email.android.com> (raw)
I stumbled over the referenced SoupTCP paper and read this paper twice. They really implemented some PPP inband signaling nowadays although processing speed is important? Every byte in the data stream must be touched to capture the end of message ... Ok
--
http://protocollabs.com
Dave Taht <dave.taht@gmail.com> schrieb:
>Occasionally I pop my head up and check into the problems data centers
>have. I knew high frequency trading had gone to extremes, but was
>unaware of just how extreme it had become.
>
>http://queue.acm.org/detail.cfm?id=2536492
>
>
>--
>Dave Täht
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat
>
next reply other threads:[~2013-10-21 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 22:31 Hagen Paul Pfeifer [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-21 20:23 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=2hfxas9kmlfvv3r80gjjsqgk.1382394693673@email.android.com \
--to=hagen@jauu.net \
--cc=bloat@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