From: Ketan Kulkarni <ketkulka@gmail.com>
To: David Lang <david@lang.hm>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bufferbloat in switches and routers
Date: Sat, 18 Apr 2015 15:12:21 -0700 [thread overview]
Message-ID: <CAD6NSj55tpB5bixC2K405Le7cGOd5dA7GQFpX2vzE7SAta2PMQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1504181326000.26044@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
On Apr 18, 2015 13:33, "David Lang" <david@lang.hm> wrote:
>
> On Sat, 18 Apr 2015, Ketan Kulkarni wrote:
>
>> Hi,
>> We have been talking about the bloated buffers mostly on the home
routers.
>> The Cisco PIE too has been standardized by docsis meant to be for cable
>> modems
>>
>> I think we would have similar concerns for switches and routers. (E.g.
>> cat3k switches or Cisco 5760 controllers just to name)
>
>
> remember that bufferbloat shows up where there is a difference in
bandwidth from one side of the router to the other (i.e. a bottleneck)
>
Thanks this makes the devices easier to target.
> This is almost always going to happen at the edge of your LAN where you
go from your Gig-E (or in a datacenter, possibly 10Gig-E to your WAN link.
It can happen at places inside your datacenter, but isn't as likely
>
Agree. As per my (limited) knowledge of such deployment goes, these
probably never run to their peak capacity in the production/live system
probably not even to saturate the lowest of the links( I may be wrong
though) . Given this, what is the gravity of the effect of the bufferbloat?
Or such study has never been done before?
Having AQM won't definitely hurt, however is it indeed a real problem to
solve for such edge routers?
At the same time I hear codel or pie finding the space in data centers. So
there are definitely some pieces I am missing.
Sorry for being little naive but the answers will definitely help me
understand the problem space and spread more awareness about bufferbloat.
>
>> I would like to know your views about what you think about it .
>> Are the theories so far and the AQMs (codel and pie) stand true for such
>> devices too?
>
>
> If they are bottlenecks, yes. If they are not bottlenecks it won't hurt
(no queues will build up
>
>
>> What would it take to measure the bloat levels of these devices? Do we
>> still need to use the netperf wrapper to get the characteristics of such
>> devices?
>
>
> the same approach works. you may need beefier systems to generate
sufficient load.
>
> David Lang
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2842 bytes --]
prev parent reply other threads:[~2015-04-18 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAD6NSj5b3sB0ayTfncbV8daSKe-K5M=PpBmBVjNL0DYWvc8CPQ@mail.gmail.com>
[not found] ` <CAD6NSj6YBFrWmOiBFgVuk3A-D6wj0NmEoo4CZwZQxAg-e=LWVw@mail.gmail.com>
2015-04-18 19:07 ` Ketan Kulkarni
2015-04-18 19:11 ` Steinar H. Gunderson
2015-04-18 19:24 ` Ketan Kulkarni
2015-04-18 19:39 ` Steinar H. Gunderson
2015-04-18 20:33 ` David Lang
2015-04-18 22:12 ` Ketan Kulkarni [this message]
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=CAD6NSj55tpB5bixC2K405Le7cGOd5dA7GQFpX2vzE7SAta2PMQ@mail.gmail.com \
--to=ketkulka@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
/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