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:02:31 -0600	[thread overview]
Message-ID: <BANLkTik38WSqz5jRSS1OB-k+pgBWwEmjgw@mail.gmail.com> (raw)
In-Reply-To: <1306686801.30021.14.camel@edumazet-laptop>

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

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

> Le dimanche 29 mai 2011 à 10:07 -0600, Dave Taht a écrit :
> >
> >
> > On Sun, May 29, 2011 at 9:51 AM, Juliusz Chroboczek
> > <jch@pps.jussieu.fr> wrote:
> >         >> Are you seeing high CPU load in interrupt context?  (Run
> >         top.)
> >
> >         > Yes. 99% sirq.
> >
> >
> >         Could be due to a simplistic Ethernet driver.  If you have the
> >         time and
> >         energy, you may want to ask on dev.openwrt.org.
> >
> > I will have some energy and time, shortly.
> >
> > That said, several great openwrt people are on this list, and may be
> > able to weigh in.
> >
> > I'm glad that the limit of about 130Mbit on the ethernet side for gigE
> > could be mitigated with a better driver. (and that said, 130Mbit is
> > "good enough" for most of the world)
> >
>
> Hmm, 130 Mbits sound very low. What linux version is it, and what the
> driver is exactly, so that I take a look ?
>
>
>
The ethernet driver is the ag71xx driver as present in the wndr3700v2 (and
mucho related atheros hardware).  Regrettably so far as I can tell, this one
is out of tree, and is incorporated in the openwrt build via a string of
patches.

https://dev.openwrt.org/browser/trunk/target/linux/ar71xx/files/drivers/net/ag71xx

I think.

Gabor sent patches for it to me for ethtool that I have not yet tried.

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...


1: http://www.bufferbloat.net/projects/bismark/wiki/Capetown
-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com

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

  reply	other threads:[~2011-05-29 16:46 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 [this message]
2011-05-29 17:17                 ` Eric Dumazet
2011-05-29 17:40                   ` Dave Taht
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=BANLkTik38WSqz5jRSS1OB-k+pgBWwEmjgw@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