From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] tiny monsters: multicast packets
Date: Sun, 29 May 2011 10:07:37 -0600 [thread overview]
Message-ID: <BANLkTi=D=aqq6fFjQZQ6PrQCtH6i-oVO9A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTim=xpuFEUPORqEZMdO_nhd_3_0c7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1694 bytes --]
sorry, I meant to reply all.
Thanks for so quickly seeing the real cause of the upper limit.
On Sun, May 29, 2011 at 10:07 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
>
> 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)
>
> On the other hand, making the switch that lays underneath this driver, work
> well, looks hard.
>
> Does anybody here speak enough Taiwanese to get enough detail on the
> rtl8366s to see what it would take to enable fair queueing and port
> mirroring?
>
> or have a relationship with realtek they could use to get this info?
>
> The datasheet has insufficient detail, and yet the switch seems enormously
> capable, at least in theory. The kind of numbers under load I've seen thus
> far (ranging from .9ms to 170ms) suggest port starvation.
>
> http://realtek.info/pdf/rtl8366s_8366sr_datasheet_vpre-1.4_20071022.pdf
>
>
>
>> -- Juliusz
>>
>
>
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://the-edge.blogspot.com
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 2975 bytes --]
next prev parent reply other threads:[~2011-05-29 15:51 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 [this message]
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
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=D=aqq6fFjQZQ6PrQCtH6i-oVO9A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.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