General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] curious.....
Date: Sun, 08 Dec 2013 18:56:34 +0100	[thread overview]
Message-ID: <87txejb50t.wl%jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <CAA93jw6PmaCLsEyAb3yHX9FxBepHt+CN=+XV+nAQ11KShpu=7Q@mail.gmail.com>


> > I think that the WNDR3800 should be able to push a gigabit, even with NAT.
> 
> No, it tops out at about 330Mbit/sec currently with no firewall rules,
> no nat.

Full-size frames?  That sucks.  (And thanks for the hard data.)

> No. aqm-scripts can't push 110KB/sec through *HTB*.

Typo?

> The rate limiter is the biggest cpu pig in the system.

Have you spoken to Dumazet about that?

> What I was thinking about was taking the 3 tier structure of the
> current aqm-scripts system, turning it into something more drr-like
> and adding support for rate limiting directly to it

(Nods.)

> Notably it seems few have internalized what the "sparse stream"
> optimization does for things like voip.

We're waiting with held breath until you care to enlighten us ;-)

-- Juliusz

  reply	other threads:[~2013-12-08 17:56 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 18:40 Outback Dingo
2013-12-03 22:25 ` Kenyon Ralph
2013-12-04  0:25   ` Outback Dingo
2013-12-04  0:38     ` Dave Taht
2013-12-06 17:19       ` Juliusz Chroboczek
2013-12-06 18:15         ` Dave Taht
2013-12-07 11:24           ` Sebastian Moeller
2013-12-10 19:05             ` Dave Taht
2013-12-11 10:44               ` Sebastian Moeller
2013-12-07 12:59           ` Juliusz Chroboczek
2013-12-08  1:27             ` Steinar H. Gunderson
2013-12-08  5:24               ` Mikael Abrahamsson
2013-12-08 11:00                 ` Mark Constable
2013-12-08 14:01                   ` Outback Dingo
2013-12-08 14:03                     ` Outback Dingo
2013-12-08 16:44                     ` Mark Constable
2013-12-08 19:00                       ` Sebastian Moeller
2013-12-08 13:12                 ` Juliusz Chroboczek
2013-12-08 16:46                   ` Jonathan Morton
2013-12-08 16:51                   ` Dave Taht
2013-12-08 17:56                     ` Juliusz Chroboczek [this message]
2013-12-08 21:05                       ` Jonathan Morton
2013-12-08 14:22                 ` Aaron Wood
2013-12-08 14:41                 ` Jim Gettys
2013-12-08 10:40             ` Sebastian Moeller
2013-12-08 13:25               ` Juliusz Chroboczek
2013-12-08 16:26                 ` Sebastian Moeller
2013-12-08 17:47                   ` Juliusz Chroboczek
2013-12-08 19:02                     ` Sebastian Moeller
2013-12-22  1:38                       ` Dan Siemon
2013-12-22  3:46                         ` Stephen Hemminger
2013-12-08 19:01                   ` Jonathan Morton
2013-12-08 19:21                     ` Sebastian Moeller
2013-12-08 16:01               ` Neil Davies
2013-12-08 20:41 Hal Murray
2013-12-08 23:16 ` Stephen Hemminger
2013-12-09  9:51 ` Sebastian Moeller

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=87txejb50t.wl%jch@pps.univ-paris-diderot.fr \
    --to=jch@pps.univ-paris-diderot.fr \
    --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