From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iw0-f171.google.com (mail-iw0-f171.google.com [209.85.214.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 7F8BD201A49 for ; Sun, 29 May 2011 08:51:48 -0700 (PDT) Received: by iwn8 with SMTP id 8so3737127iwn.16 for ; Sun, 29 May 2011 09:07:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Sicn5a/GAsERQ2+Fol0MM5vHjq7T+Q7UfyChl3z2nS0=; b=vi/oojfXAXHlTJ28JaJZMtkLDam/QyBLF4hUYuV2I6lV9demX62OuMkGm8YYagVQi6 CRX0TWFH/+eCWL0me+RpX8ndtwfmQId5+9nbIvEMj/ISZVljwJ6ZGDri6+kqbWSk1iz0 jl+PLacsKF4GNU8Obr9hwlgpcjVfNh5R+zrAk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=EdM8HMAX+v3yyLpQZqwdx+CacF24GjY/mELMxzeqEEfF1s5y974Gai681c/6SUCoM3 KR3HXhK+BL/5tjAkUig9wwhg1ir5VVzzKJSIvo22UEglUcYsdO2quDuyGVOM1689+nzR CFHaeQDZRX0L9ReL63k8IvM1Ldxei8NkNk56g= MIME-Version: 1.0 Received: by 10.42.94.6 with SMTP id z6mr6081560icm.91.1306685257360; Sun, 29 May 2011 09:07:37 -0700 (PDT) Received: by 10.231.39.203 with HTTP; Sun, 29 May 2011 09:07:37 -0700 (PDT) In-Reply-To: References: <7ifwnxbjyn.fsf@lanthane.pps.jussieu.fr> <7i62otpks1.fsf@lanthane.pps.jussieu.fr> Date: Sun, 29 May 2011 10:07:37 -0600 Message-ID: From: Dave Taht To: bloat Content-Type: multipart/alternative; boundary=20cf3036405f99271404a46c5e0f Subject: Re: [Bloat] tiny monsters: multicast packets X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 15:51:48 -0000 --20cf3036405f99271404a46c5e0f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 wrote: > > > On Sun, May 29, 2011 at 9:51 AM, Juliusz Chroboczek w= rote: > >> >> 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, wo= rk > 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 enormousl= y > capable, at least in theory. The kind of numbers under load I've seen thu= s > far (ranging from .9ms to 170ms) suggest port starvation. > > http://realtek.info/pdf/rtl8366s_8366sr_datasheet_vpre-1.4_20071022.pdf > > > >> -- Juliusz >> > > > > -- > Dave T=E4ht > SKYPE: davetaht > US Tel: 1-239-829-5608 > http://the-edge.blogspot.com > --=20 Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 http://the-edge.blogspot.com --20cf3036405f99271404a46c5e0f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable sorry, I meant to reply all.

Thanks for so quickly seeing the real c= ause 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? =A0(Run to= p.)

> Yes. 99% sirq.

Could be due to a simplistic Ethernet driver. =A0If 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, sever= al 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=20 could be mitigated with a better driver. (and that said, 130Mbit is=20 "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=20 rtl8366s to see what it would take to enable fair queueing and port=20 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=20 capable, at least in theory. The kind of numbers under load I've seen= =20 thus far (ranging from .9ms to 170ms) suggest port starvation.

http://realtek.info/pdf/rtl8366s_8366sr_data= sheet_vpre-1.4_20071022.pdf

=A0
-- Juliusz



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



--
Dave T=E4ht=
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
--20cf3036405f99271404a46c5e0f--