From: dpreed@reed.com
To: "Jim Gettys" <jg@freedesktop.org>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
bloat-devel <bloat-devel@lists.bufferbloat.net>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
blogic@openwrt.org
Subject: Re: [Cerowrt-devel] hardware hacking on fq_codel in FPGA form at 10GigE
Date: Fri, 21 Dec 2012 14:34:04 -0500 (EST) [thread overview]
Message-ID: <1356118444.43673943@apps.rackspace.com> (raw)
In-Reply-To: <CAGhGL2DC0o_wzO9f12b0i0UXeB4BKhst-aQHfoBiztLU3KAPOw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6126 bytes --]
Understand about the chip vendors. It is the case, though, that system vendors often have NDA's with the chip vendors ... and they are the immediate customer of the chip vendors, so have some leverage to get their help resolving the issues.
I think the first step is doing the right measurements, to show that the chip is a bottleneck (as you are doing with Lantiq).
-----Original Message-----
From: "Jim Gettys" <jg@freedesktop.org>
Sent: Friday, December 21, 2012 1:45pm
To: "David P Reed" <dpreed@reed.com>
Cc: "Dave Taht" <dave.taht@gmail.com>, "bloat-devel" <bloat-devel@lists.bufferbloat.net>, "cerowrt-devel@lists.bufferbloat.net" <cerowrt-devel@lists.bufferbloat.net>, "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>, blogic@openwrt.org
Subject: Re: [Cerowrt-devel] hardware hacking on fq_codel in FPGA form at 10GigE
On Fri, Dec 21, 2012 at 1:25 PM, <[mailto:dpreed@reed.com] dpreed@reed.com> wrote:
I'm sure the HSPA+ modem is a binary blob. For regulatory reasons, if nothing else...
When I said open, I did not mean the ultimate ideal. Hardware devices with firmware are often sold as black boxes.
Fixing the bloat in HSPA+ and LTE systems will require organizations like Ericsson, ALU and Cisco and Huawei to get their acts together and fix their own bugs.
Actually, this needs probably/certainly needs help from the chip vendors as well as the system vendors. The system vendors (such as ALU) often get their chips and drivers from those chip vendors.
I haven't looked into the HSPA+ or LTE systems; I am looking into DSL. In the DSL concrete example, Broadcom controls the bulk of the DSL chip market, and (at least on the client home router end) provides a binary blob Linux driver based on an antique Linux release (2.6.26, IIRC). The hardware itself did not look like it had bad buffering, but the drivers....
I've been working with blogic (John Crispin) on debloating the Lantiq driver, which we are trying to test; since it is entirely open source. In the Lantiq DSL driver case, the hardware sprouted exactly the same sort of transmit/receive rings found in ethernet drivers, with the corresponding bufferbloat due to device drivers being totally stupid. Unfortunately, BQL is ethernet only, and right now doesn't work properly at low bandwidths.
When John cut the transmit ring down to 2 packets, the latency dropped (at the bandwidth he was testing at, .5Mbps) to around 60ms running fq_codel, about what you would expect given the remaining buffers; we have to automate the control of the transmit ring properly (since we probably do need some help when running VDSL at 100Mbps).
I suspect/expect we'll find similar "features" when we dig into LTE and HSPA+, though that is not certain.
Now, back to my saga of my recalcitrant water well, after which I can go back to testing DSL the next trip to New Jersey (and flush the toilets and have heat; I have geothermal heat...).
Sigh,
- Jim
-----Original Message-----
From: "Jim Gettys" <[mailto:jg@freedesktop.org] jg@freedesktop.org>
Sent: Friday, December 21, 2012 1:14pm
To: "David P Reed" <[mailto:dpreed@reed.com] dpreed@reed.com>
Cc: "Dave Taht" <[mailto:dave.taht@gmail.com] dave.taht@gmail.com>, "bloat-devel" <[mailto:bloat-devel@lists.bufferbloat.net] bloat-devel@lists.bufferbloat.net>, "[mailto:cerowrt-devel@lists.bufferbloat.net] cerowrt-devel@lists.bufferbloat.net" <[mailto:cerowrt-devel@lists.bufferbloat.net] cerowrt-devel@lists.bufferbloat.net>, "[mailto:codel@lists.bufferbloat.net] codel@lists.bufferbloat.net" <[mailto:codel@lists.bufferbloat.net] codel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] hardware hacking on fq_codel in FPGA form at 10GigE
On Fri, Dec 21, 2012 at 12:48 PM, <[mailto:dpreed@reed.com] dpreed@reed.com> wrote:
And if you want an open tablet the ODROID U2 there is pretty nice for <$900 all in, including an HSPA+ modem w/GPS. I can only imagine what one can do with this....
Often the modem bits are binary blobs. Any information on this front?
- Jim
-----Original Message-----
From: "Dave Taht" <[mailto:dave.taht@gmail.com] dave.taht@gmail.com>
Sent: Friday, December 21, 2012 7:34am
To: [mailto:dpreed@reed.com] dpreed@reed.com
Cc: "Hal Murray" <[mailto:hmurray@megapathdsl.net] hmurray@megapathdsl.net>, "bloat-devel" <[mailto:bloat-devel@lists.bufferbloat.net] bloat-devel@lists.bufferbloat.net>, [mailto:codel@lists.bufferbloat.net] codel@lists.bufferbloat.net, [mailto:cerowrt-devel@lists.bufferbloat.net] cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] hardware hacking on fq_codel in FPGA form at 10GigE
It really is astounding what is going on in the arm world:
[http://www.hardkernel.com/renewal_2011/products/prdt_info.php?g_code=G135341370451] http://www.hardkernel.com/renewal_2011/products/prdt_info.php?g_code=G135341370451
> The wndr3700v4 is out, and appears to be a good hardware upgrade from
> the 3800 series, but it's not supported by openwrt yet.
>
> I took a look at their GPL source distribution. And yea! it's openwrt.
> And boo! it's ancient openwrt, for example dnsmasq is 2.39 (current is
> 2.64), and their kernel is 2.6.31.
>
> I think the cpu and ethernet chips tho look a lot better: Atheros
> AR9344+ AR9580(5GHz)+AR9344(2.4GHz). It's my hope these do ipv6
> better.
>
> I have looked at similar products from buffalo and others, would like
> external antennas and a good switch this time around. Thoughts?
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: [http://www.teklibre.com/cerowrt/subscribe.html] http://www.teklibre.com/cerowrt/subscribe.html
--
Dave Täht
Fixing bufferbloat with cerowrt: [http://www.teklibre.com/cerowrt/subscribe.html] http://www.teklibre.com/cerowrt/subscribe.html
_______________________________________________
Bloat-devel mailing list
[mailto:Bloat-devel@lists.bufferbloat.net] Bloat-devel@lists.bufferbloat.net
[https://lists.bufferbloat.net/listinfo/bloat-devel] https://lists.bufferbloat.net/listinfo/bloat-devel
[-- Attachment #2: Type: text/html, Size: 9514 bytes --]
next prev parent reply other threads:[~2012-12-21 19:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dave.taht@gmail.com>
2012-12-20 7:28 ` Dave Taht
2012-12-20 8:17 ` Hal Murray
2012-12-20 8:27 ` Jonathan Morton
2012-12-20 9:51 ` Hal Murray
2012-12-20 9:13 ` Dave Taht
2012-12-20 9:26 ` Dave Taht
2012-12-20 10:32 ` Hal Murray
2012-12-20 13:53 ` [Cerowrt-devel] " dpreed
2012-12-20 14:18 ` Dave Taht
2012-12-20 15:05 ` Dave Taht
2012-12-21 12:34 ` Dave Taht
2012-12-21 17:48 ` dpreed
2012-12-21 18:14 ` Jim Gettys
2012-12-21 18:25 ` dpreed
2012-12-21 18:45 ` Jim Gettys
2012-12-21 19:34 ` dpreed [this message]
2012-12-21 19:42 ` Jim Gettys
2012-12-21 21:54 ` [Codel] " David Woodhouse
2012-12-21 21:56 ` John Crispin
2012-12-21 22:08 ` David Woodhouse
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1356118444.43673943@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=blogic@openwrt.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=jg@freedesktop.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