From: David Woodhouse <dwmw2@infradead.org>
To: Jim Gettys <jg@freedesktop.org>, blogic@openwrt.org
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
David P Reed <dpreed@reed.com>,
"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
blogic@openwrt.org
Subject: Re: [Codel] [Cerowrt-devel] hardware hacking on fq_codel in FPGA form at 10GigE
Date: Fri, 21 Dec 2012 21:54:03 +0000 [thread overview]
Message-ID: <1356126843.2420.35.camel@shinybook.infradead.org> (raw)
In-Reply-To: <CAGhGL2DC0o_wzO9f12b0i0UXeB4BKhst-aQHfoBiztLU3KAPOw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
On Fri, 2012-12-21 at 13:45 -0500, Jim Gettys wrote:
>
> 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.
Hmmm. With the code that's currently in OpenWRT, we shouldn't *let* the
ATM driver have a huge queue of packets unless it's doing something
egregiously stupid like calling the vcc->pop() function on the skb
before it's actually sent it.
PPPoATM for a long time has limited the queue at the hardware driver to
2 packets, instead of a full sock_wmem's worth of buffers like it used
to in the past. Since a couple of weeks ago the BR2684 driver
(Ether-over-ATM, as used with PPPoE on top) also does the same thing.
So the ATM driver would have to go out of its way to screw you over¹.
John?
Btw, I'm looking at ways to *make* BQL on the PPP netdev work properly,
tracking packets all the way to the wire even when it's PPPoA,
PPPoE(oA), L2TP or whatever.
--
dwmw2
¹ Unless you're using IP over ATM directly. I haven't looked at that one.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
next prev parent reply other threads:[~2012-12-21 21:54 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 ` [Codel] " 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 ` [Codel] [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
2012-12-21 19:42 ` Jim Gettys
2012-12-21 21:54 ` David Woodhouse [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1356126843.2420.35.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=blogic@openwrt.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=dpreed@reed.com \
--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