From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Scheffenegger, Richard" <rs@netapp.com>
Cc: "iccrg@irtf.org" <iccrg@irtf.org>, "aqm@ietf.org" <aqm@ietf.org>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [iccrg] [aqm] AQM deployment status?
Date: Sat, 28 Sep 2013 08:59:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1309280855590.32315@uplift.swm.pp.se> (raw)
In-Reply-To: <012C3117EDDB3C4781FD802A8C27DD4F25D969C5@SACEXCMBX02-PRD.hq.netapp.com>
On Fri, 27 Sep 2013, Scheffenegger, Richard wrote:
> Hi Mikael,
>
> the papers around DCTCP have probably the information you are looking
> for (map/reduce type workloads, leading to incast issues - momentary
> filling of queues; loosing the final segments of a TCP session [1],
> which is likely with drop tail queue management policy, is well known to
> result in timely retransmission timeout-type recoveries. Tweaking OS
> time granularities down to recover in few milliseconds on paths that
> usually have a few dozen microseconds delay is often not good enough,
> but even that is not for cautious.
Ok, so this makes sense within a data center with ECN, but I fail to see
any substantial upside deploying this in an environment where RTT is in
the tens of ms because TCP won't have time to react.
I seem to remember reading about enhancement to TCP where packets are
actually sent out with spacing between packets instead of in line-rate
bursts. If everybody started doing that then I would imagine there would
be less tail-drop in large RTT environments with large TCP windows?
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2013-09-28 6:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 17:21 [Bloat] " Naeem Khademi
2013-09-24 17:24 ` [Bloat] [aqm] " LOCHIN Emmanuel
2013-09-25 14:20 ` Akhtar, Shahid (Shahid)
2013-09-25 14:31 ` [Bloat] [iccrg] " Eggert, Lars
2013-09-25 14:35 ` Steinar H. Gunderson
2013-09-25 18:51 ` Akhtar, Shahid (Shahid)
2013-09-25 19:19 ` [Bloat] [aqm] [iccrg] " Naeem Khademi
2013-09-27 16:49 ` Akhtar, Shahid (Shahid)
2013-09-25 19:24 ` Mikael Abrahamsson
2013-09-26 9:39 ` [Bloat] [iccrg] [aqm] " Scheffenegger, Richard
2013-09-27 2:59 ` Mikael Abrahamsson
2013-09-27 9:06 ` Eggert, Lars
2013-09-28 7:01 ` Mikael Abrahamsson
2013-09-28 7:04 ` Eggert, Lars
2013-09-29 1:16 ` [Bloat] [aqm] [iccrg] " Bob Briscoe
2013-09-29 9:37 ` Mikael Abrahamsson
2013-09-27 13:53 ` [Bloat] [iccrg] [aqm] " Scheffenegger, Richard
2013-09-28 6:59 ` Mikael Abrahamsson [this message]
2013-11-13 17:50 ` [Bloat] [aqm] [iccrg] " Fred Baker (fred)
2013-10-12 3:18 ` [Bloat] [iccrg] [aqm] " Michael Richardson
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=alpine.DEB.2.02.1309280855590.32315@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=iccrg@irtf.org \
--cc=rs@netapp.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