From: "René van Dorst" <opensource@vdorst.com>
To: wireguard@lists.zx2c4.com
Subject: Re: "The OpenWRT Commit" (native chacha20 mips32 support)
Date: Wed, 23 May 2018 06:55:02 +0000 [thread overview]
Message-ID: <20180523065502.Horde.XmS-X9MeW68pkcgw65-pNRx@www.vdorst.com> (raw)
In-Reply-To: <CY4PR14MB11417381F5FD378FE994F0A1A2940@CY4PR14MB1141.namprd14.prod.outlook.com>
Quoting Denis Kisselev <denis@dkisselev.net>:
> Has anyone had a chance to play around with the new snapshot
> (<https://git.zx2c4.com/WireGuard/commit/?id=d67d89c7f9d83d22d750452236b0e16510ab1368>0.0.20180519<https://git.zx2c4.com/WireGuard/tag/?h=0.0.20180519>) on a mips
> device?
>
>
> It looks like ChaCha20 is now natively supported but I'm curious
> about what kind of performance people are now seeing on devices.
>
>
> Anecdotally, it looks like people were getting 50-60mbps on ~650mhz
> devices like the AR-300M when wireguard made its first splash about
> a year ago.
Chacha20 routine is around 114-117% faster.
Poly1305 routine is around ~275% faster.
Both compared with generic C version.
So you will see a 10-25% improvement in the speed.
Greats,
René van Dorst.
prev parent reply other threads:[~2018-05-23 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 21:23 "The OpenWRT Commit" (native chacha20 mips32 support) Denis Kisselev
2018-05-23 6:55 ` René van Dorst [this message]
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=20180523065502.Horde.XmS-X9MeW68pkcgw65-pNRx@www.vdorst.com \
--to=opensource@vdorst.com \
--cc=wireguard@lists.zx2c4.com \
/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;
as well as URLs for NNTP newsgroup(s).