From: Michael Richardson <mcr@sandelman.ca>
To: cerowrt-devel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] still trying to find hardware for the next generation worth hacking on
Date: Mon, 18 Aug 2014 20:34:05 -0400 [thread overview]
Message-ID: <16167.1408408445@sandelman.ca> (raw)
In-Reply-To: <CAA93jw7eq7D=xR4_KgY1s9y+3LBJhLFUpXdsEc7ZaYtDWOKh_w@mail.gmail.com>
Dave Taht <dave.taht@gmail.com> wrote:
> In the cases where we can make a difference, the only cpu technologies
> that appear
> capable of doing GigE and software rate limiting and codel seem to be
> x86 based. (And only intel! even a amd box, recently benchmarked,
> couldn't forward at > 700Mbit)
Benchmarked how?
I would suspect that it's not CPU, but rather network/memory bottlenecks,
as well as L1/memory bottleneck.
A number of years ago there was
Combo6... https://www.liberouter.org/comboi-1g4-4-%C3%97-1ge/
This is *NOT* consumer grade, clearly, but maybe it would attract something.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2014-08-19 0:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 20:33 [Bloat] " Dave Taht
2014-08-15 20:51 ` Eric S. Raymond
2014-08-15 21:02 ` Dave Taht
2014-08-15 21:21 ` Jonathan Morton
2014-08-16 0:46 ` [Bloat] [Cerowrt-devel] " David P. Reed
2014-08-16 20:41 ` [Bloat] " Michael Richardson
2014-08-17 17:13 ` [Bloat] [Cerowrt-devel] " dpreed
2014-08-18 20:51 ` Frank Carmickle
2014-08-18 22:00 ` Dave Taht
2014-08-19 0:34 ` Michael Richardson [this message]
2014-08-22 3:11 ` Dave Taht
[not found] ` <lstjkh$k82$1@ger.gmane.org>
2014-08-18 20:09 ` Aaron Wood
2015-03-09 12:53 ` Guillaume Fortaine
2015-03-09 13:11 ` Sebastian Moeller
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16167.1408408445@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-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