General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Gabor Juhos <juhosg@openwrt.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] tiny monsters: multicast packets
Date: Sun, 29 May 2011 11:40:17 -0600	[thread overview]
Message-ID: <BANLkTi=mhS+u-NkuFS2fM5WDJR_jeO4KWA@mail.gmail.com> (raw)
In-Reply-To: <1306689449.30021.16.camel@edumazet-laptop>

[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]

On Sun, May 29, 2011 at 11:17 AM, Eric Dumazet <eric.dumazet@gmail.com>wrote:

> Le dimanche 29 mai 2011 à 11:02 -0600, Dave Taht a écrit :
>
> > The kernel being used in capetown[1] is 2.6.37.6. - patched forward
> > from 2.6.39 for the pfifo ecn bug, the ipv6 ecn bug, and several other
> > bufferbloat related things like sfb...
> >
>
> Hmm, maybe you could try "perf top" if available to make sure cpu time
> is used in this driver, not in another layer ?
>
>
>
>
perf-top does not appear to have been ported to openwrt, and as cool as it
is, I do not know if the related performance counters exist for mips.

it would be darn useful though.

All I know at the moment is that sirq is at 99% at the given workload,
according busybox's top.

http://www.bufferbloat.net/attachments/download/33/routertest.png

It is mildly early to point at the driver as being the issue - it could be
the switch or something else entirely. Would iptables or qos rules show up
in sirq?


-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com

[-- Attachment #2: Type: text/html, Size: 1612 bytes --]

  reply	other threads:[~2011-05-29 17:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-29 13:23 Dave Taht
2011-05-29 14:10 ` Jonathan Morton
2011-05-29 15:10   ` Dave Taht
2011-05-29 15:33     ` Juliusz Chroboczek
2011-05-29 15:44       ` Dave Taht
2011-05-29 15:51         ` Juliusz Chroboczek
2011-05-29 16:07           ` Dave Taht
2011-05-29 16:07             ` Dave Taht
2011-05-29 16:53               ` Dave Taht
2011-05-29 16:33             ` Eric Dumazet
2011-05-29 17:02               ` Dave Taht
2011-05-29 17:17                 ` Eric Dumazet
2011-05-29 17:40                   ` Dave Taht [this message]
2011-05-29 17:47                     ` Jonathan Morton
2011-05-29 19:14                     ` Eric Dumazet
2011-05-29 15:21   ` Juliusz Chroboczek
2011-05-29 15:57     ` Dave Taht
2011-05-31 14:58       ` Jim Gettys

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='BANLkTi=mhS+u-NkuFS2fM5WDJR_jeO4KWA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=eric.dumazet@gmail.com \
    --cc=juhosg@openwrt.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