From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "iccrg@irtf.org" <iccrg@irtf.org>
Cc: "aqm@ietf.org" <aqm@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [aqm] [iccrg] AQM deployment status?
Date: Wed, 25 Sep 2013 21:24:56 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1309252118590.32315@uplift.swm.pp.se> (raw)
In-Reply-To: <C0611F522A6FA9498A044C36073E49656D91899C@US70UWXCHMBA01.zam.alcatel-lucent.com>
On Wed, 25 Sep 2013, Akhtar, Shahid (Shahid) wrote:
> Please see below examples of support for RED/WRED from switches (from ALU and Cisco websites, search for RED or WRED in document):
I'd venture to claim that putting RED on a device with a few milliseconds
worth of buffer depth is pretty much useless (for instance the Cisco 6704
or 6724 linecards). So most datacenter equipment doesn't have this, or if
they do, it's not that usable even if they had (who cares about drop
probability when taildrop is being done at 4-5 ms buffer depth?).
For higher end platforms, for instance all cisco CPU based routers (for
some value of "all") can be configured with RED, fair-queue or similar,
but they come with FIFO as default. This has been the same way since at
least the mid 90ties as far as I know, long way back to cisco 1600 device
etc.
Higher end Cisco equipment such as ASR9k, 12000, CRS etc, all support
WRED, and here it makes sense since they all have ~50ms worth of buffering
or more. They also come with FIFO as default setting.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2013-09-25 19:24 UTC|newest]
Thread overview: 22+ 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 [this message]
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
2013-11-13 17:50 ` [Bloat] [aqm] [iccrg] " Fred Baker (fred)
2013-10-12 3:18 ` [Bloat] [iccrg] [aqm] " Michael Richardson
[not found] <Your message of "Fri, 11 Oct 2013 23:18:05 EDT." <12845.1381547885@sandelman.ca>
[not found] ` <201310141707.r9EH7wC7068478@gateway1.orleans.occnc.com>
2013-10-16 1:00 ` [Bloat] [aqm] [iccrg] " Wesley Eddy
2013-11-05 2:56 ` Bob Briscoe
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.1309252118590.32315@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=iccrg@irtf.org \
/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