From: Dave Taht <dave.taht@gmail.com>
To: Hal Murray <hmurray@megapathdsl.net>
Cc: codel@lists.bufferbloat.net,
bloat-devel <bloat-devel@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: hardware hacking on fq_codel in FPGA form at 10GigE
Date: Thu, 20 Dec 2012 04:26:37 -0500 [thread overview]
Message-ID: <CAA93jw7Hr3fiVf3n9u4f6s4HHaBjzcbFN558On+fBcJ9WGYusg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5ahao=o4Efp6zDqgFaQoJGLxv0k=v3rVnNskFB=c9oGA@mail.gmail.com>
On Thu, Dec 20, 2012 at 4:13 AM, Dave Taht <dave.taht@gmail.com> wrote:
> On Thu, Dec 20, 2012 at 3:17 AM, Hal Murray <hmurray@megapathdsl.net> wrote:
>>
>> If I was going to do something like that, I'd build a small/simple CPU and do
>> the work in microcode.
I'd also looked at the octeon and the latest arm chipset from TI which
I can't remember the codename for at the moment...
http://www.cavium.com/OCTEON-II_CN68XX.html
Looks like cavium is going ARM with their next chip.
I'd certainly like to see an IP block for arm socs for this stuff too.
Given the huge number of offloads in the network path on most upcoming
SOCs, it's going to be hard to wedge queue management on top in
software. See, for example, the mindspeed C2000. So it seems like
finding an arm design house to get an IP block for fq_codel put
together is in order.
There are a couple interesting hybrid fpga/arm chips from places like st micro.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2012-12-20 9:26 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 [this message]
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
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=CAA93jw7Hr3fiVf3n9u4f6s4HHaBjzcbFN558On+fBcJ9WGYusg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=hmurray@megapathdsl.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