Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net,
	 bloat-devel <bloat-devel@lists.bufferbloat.net>,
	codel@lists.bufferbloat.net
Subject: hardware hacking on fq_codel in FPGA form at 10GigE
Date: Thu, 20 Dec 2012 02:28:19 -0500	[thread overview]
Message-ID: <CAA93jw7h8d5Y8r+_DwR_cF9F7TEWzgZuoYvfOWp5B=1=pGx=BQ@mail.gmail.com> (raw)

see: http://netfpga.org/

The quad gig-E version looks like it works well (in that there are
advanced things like DRR available for it) but the underlying FPGA is
obsolete. The quad 10GigE version looks sexy but not very functional
as yet. In either case, implementing {n,e,s}fq_codel onboard looks
very feasible, although something of a larger effort than I'd like to
spend personally. (it's been about 6 years since I last touched
verilog)

I would be interested however in getting a bunch of hardware hackers
together (and getting the academic discount on this board) to try and
do an implementation of a fq_codel derivative on the quad 10GigE
board. (or I would be happy to learn of some group already doing it)

The only thing that is seriously serial about fq_codel is shooting the
biggest flow when the queue limit is exceeded, and that could be made
embarrassingly parallel with enough gates.There are no doubt other
tricky issues.

I would like it if we could match the ns2 model entirely... down to
the last packet... in the real world. I have few contacts at stanford,
presently.

https://mailman.stanford.edu/pipermail/netfpga-announce/2012-October/000094.html

There are a couple of other alternatives in the GigE space and below
on openers....

-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

             reply	other threads:[~2012-12-20  7:28 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 [this message]
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
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='CAA93jw7h8d5Y8r+_DwR_cF9F7TEWzgZuoYvfOWp5B=1=pGx=BQ@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 \
    /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