From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Matt Taggart <matt@lackof.org>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Looking for MORE SQM Router Recommendations !
Date: Wed, 17 Mar 2021 11:54:08 +0100 [thread overview]
Message-ID: <874khadp9r.fsf@toke.dk> (raw)
In-Reply-To: <e0abb6d5-d110-9d04-4ae2-403642764d23@lackof.org>
Matt Taggart <matt@lackof.org> writes:
> On 3/16/21 11:30 AM, Charles Rothschild via Cerowrt-devel wrote:
>
> > I want a 1GB capable SQM router. What options are good nowadays hw wise?
>
> I've been using the Qotom x86 boxes and running x86 OpenWRT on them.
> They have no problem doing CAKE on 1gig symmetrical connection.
>
> http://qotom.net/ and then Products -> Mini PC -> Multiple NIC
>
> But the Qotom vendor site is confusing and also doesn't list all the
> products you can find available. So a while ago I made this decoder ring
>
> https://we.riseup.net/lackof/x86-router-candidates#qotom
Nice list! One comment - the page says this:
> The Intel AES-NI cpu extension can really help openssl/wireguard a lot
That is true for openssl (and other TLS, even IPSec, I think), but not
for wireguard - that doesn't use AES at all, but rather ChaCha20, which
is not accelerated by AES-NI (and doesn't need it either).
-Toke
next prev parent reply other threads:[~2021-03-17 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1287379027.1155590.1615919208363.ref@mail.yahoo.com>
2021-03-16 18:26 ` Charles Rothschild
[not found] ` <mailman.2387.1615919214.24343.cerowrt-devel@lists.bufferbloat.net>
2021-03-16 22:03 ` [Cerowrt-devel] " Jonathan Morton
2021-03-16 22:04 ` Dave Taht
2021-03-16 22:14 ` Jonathan Morton
2021-03-16 22:58 ` Michael Richardson
2021-03-17 1:01 ` David Lang
2021-03-17 2:57 ` Jonathan Morton
2021-03-17 6:11 ` Sebastian Moeller
2021-03-17 3:06 ` Matt Taggart
2021-03-17 10:54 ` Toke Høiland-Jørgensen [this message]
[not found] ` <mailman.2393.1615978451.24343.cerowrt-devel@lists.bufferbloat.net>
2021-03-19 4:23 ` Aaron Wood
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874khadp9r.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=matt@lackof.org \
/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