From: louis <louis@ukl-1.com>
To: WireGuard <WireGuard@lists.zx2c4.com>
Subject: Hardware acceleration
Date: Sat, 9 Mar 2019 12:45:42 +0800 [thread overview]
Message-ID: <tencent_E00004E5DFAED0E0A9E47E70@qq.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 671 bytes --]
Dear team,
I’m trying to make Wireguard use CPU’s hardware crypto engine . The hardware crypto engine can be driven by linux kernel. And it has registered the algorithms which it supports to the linux kernel as I can see those by “cat /proc/crypto”. Unfortunately , there’s no CHACHA available. Is there any good suggestions about how I can make Wireguard use the engine?
Such as change the crypto suite to “GCM-AES”? Or other greater?
Hope to hear you.
Regards.
Louis Michael Networking Architect
Tel.: +86 185 0008 4208
E-Mail:louis@ukl-1.com
Web site:www.ukl-1.com
Address:Room 50629, 6F,Building D, Galaxy SOHO, Dongcheng District, Beijing, China
[-- Attachment #1.2: Type: text/html, Size: 2664 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-03-20 22:47 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=tencent_E00004E5DFAED0E0A9E47E70@qq.com \
--to=louis@ukl-1.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).