From: David Lang <david@lang.hm>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] ipspace.net: "QUEUING MECHANISMS IN MODERN SWITCHES"
Date: Wed, 28 May 2014 11:44:52 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1405281140500.32611@nftneq.ynat.uz> (raw)
In-Reply-To: <CAPh34md=TBwWUKugZTvipXhAGmjcCxe-X8dcDw9PxvqeLVh_4A@mail.gmail.com>
On Tue, 27 May 2014, Hagen Paul Pfeifer wrote:
> The question is if (codel/pie/whatever) AQM makes sense at all for
> 10G/40G hardware and higher performance irons? Igress/egress bandwidth
> is nearly identical, a larger/longer buffering should not happen. Line
> card memory is limited, a larger buffering is defacto excluded.
what if your router has more than two 40G interfaces? then you can have traffic
patters where traffic inbound on connections #1 and #2 are trying to go out #3
at a rate higher than it can handle.
At that point, you have two options
1. drop the packets
2. buffer them and hope that this is a temporary spike
if you buffer them, then the question of what queuing to use, simple FIFO,
codel, or ??? as well as how large the buffer should be allowed to grow before
you start dropping (at which point, which packets do you drop)
So I think that even on such big iron devices, there is room for the same sort
of queueing options as for lower speed connections, but processor speed and
memory size may limit how much you can do.
David Lang
next prev parent reply other threads:[~2014-05-28 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 8:21 Hagen Paul Pfeifer
2014-05-27 10:45 ` Neil Davies
2014-05-27 12:20 ` Hagen Paul Pfeifer
2014-05-27 12:34 ` Neil Davies
2014-05-28 18:44 ` David Lang [this message]
2014-05-28 9:39 Hal Murray
2014-05-28 11:00 ` Jonathan Morton
2014-05-28 18:56 ` David Lang
2014-05-28 22:15 ` Bill Ver Steeg (versteb)
2014-05-29 7:20 ` Neil Davies
2014-05-29 14:06 ` Jonathan Morton
2014-05-29 16:58 ` 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=alpine.DEB.2.02.1405281140500.32611@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=hagen@jauu.net \
/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