From: David Woodhouse <dwmw2@infradead.org>
To: John Crispin <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>
Subject: Re: [Codel] [Cerowrt-devel] hardware hacking on fq_codel in FPGA form at 10GigE
Date: Fri, 21 Dec 2012 22:08:23 +0000 [thread overview]
Message-ID: <1356127703.2420.38.camel@shinybook.infradead.org> (raw)
In-Reply-To: <50D4DB23.1010306@openwrt.org>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Fri, 2012-12-21 at 22:56 +0100, John Crispin wrote:
> > So the ATM driver would have to go out of its way to screw you over¹.
> John?
>
> the lantiq atm/dsl drivers use a dma ring to push packets from the atm
> layer to the dsl modem core. this ring needs to be 2 packets big as a
> minimum to have the hardware work. however, using software we can make
> sure that only 1 packet at a tim eis inside the ring. this is what my
> current dirty hack does.
You shouldn't need that hack any more. With the current core ATM code
you should only have two packets in the queue anyway — the one the
hardware is *currently* working on, and the next one ready to be sent
(which is necessary to avoid introducing too much latency between
packets. Your ADSL uplink is *very* limited, and you really want to be
sure you're using it *all*).
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
prev parent reply other threads:[~2012-12-21 22:08 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
2012-12-21 21:56 ` John Crispin
2012-12-21 22:08 ` David Woodhouse [this message]
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=1356127703.2420.38.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 \
/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