From: Dave Taht <dave.taht@gmail.com>
To: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: 10GigE hw?
Date: Thu, 23 Feb 2012 17:52:24 +0000 [thread overview]
Message-ID: <CAA93jw5ku6t2ah8xSQA7-DRAc2UA+vMBY41DJsFJyN7RK6Crgg@mail.gmail.com> (raw)
I am hoping to add some 10GigE capable hardware to the mix at bloatlab
#1. There is a profusion of such, and I see there is BQL support for
several devices in that range now.
any recommendations? Specifically I'd like to be playing with
something that can exercise mqprio, and/or is otherwise multi-queued
in hardware.
On the really high end the octeon stuff looked fun, but getting it to
do what I really want (implement sfqred and/or qfq in hardware) looks
like far more work than I'd be willing to take on. There was also a
lower end device from moto (name escapes me at the moment) that did
wred in hardware. My principal interest on this sort of hardware is to
find abstractions that can push up aqm concepts up and down the stack
from the hardware.
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
reply other threads:[~2012-02-23 17:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw5ku6t2ah8xSQA7-DRAc2UA+vMBY41DJsFJyN7RK6Crgg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat-devel@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