From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: openwrt@bitsofnetworks.org, lede-dev@lists.infradead.org,
wireguard@lists.zx2c4.com
Subject: [WireGuard] [PATCH] wireguard: select parallel encryption engine
Date: Thu, 10 Nov 2016 04:08:15 +0100 [thread overview]
Message-ID: <20161110030815.6531-1-Jason@zx2c4.com> (raw)
In-Reply-To: <20161110030744.6402-1-Jason@zx2c4.com>
On non SMP systems, this doesn't wind up doing anything or adding any
code at all. On SMP systems, this adds a little bit of code, and makes
encryption use all cores.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
---
net/wireguard/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/wireguard/Makefile b/net/wireguard/Makefile
index 7387673..c5c014c 100644
--- a/net/wireguard/Makefile
+++ b/net/wireguard/Makefile
@@ -89,7 +89,7 @@ define KernelPackage/wireguard
CATEGORY:=Kernel modules
SUBMENU:=Network Support
TITLE:=Wireguard kernel module
- DEPENDS:=@IPV6 +kmod-udptunnel4 +kmod-udptunnel6 +kmod-ipt-hashlimit
+ DEPENDS:=@IPV6 +@KERNEL_CRYPTO_PCRYPT +kmod-udptunnel4 +kmod-udptunnel6 +kmod-ipt-hashlimit
FILES:= $(PKG_BUILD_DIR)/src/wireguard.$(LINUX_KMOD_SUFFIX)
AUTOLOAD:=$(call AutoLoad,33,wireguard)
endef
--
2.10.2
next prev parent reply other threads:[~2016-11-10 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 3:07 [WireGuard] [PATCH] kernel: expose configuration for padata Jason A. Donenfeld
2016-11-10 3:08 ` Jason A. Donenfeld [this message]
2016-11-10 12:15 ` [WireGuard] [PATCH] wireguard: select parallel encryption engine Baptiste Jonglez
2016-11-14 8:28 ` [WireGuard] [LEDE-DEV] [PATCH] kernel: expose configuration for padata Felix Fietkau
2016-11-14 13:16 ` [WireGuard] [PATCH] kernel: enable pcrypt Jason A. Donenfeld
2016-11-16 19:35 ` Jason A. Donenfeld
2016-11-16 19:35 ` Felix Fietkau
2016-11-16 19:36 ` Jason A. Donenfeld
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=20161110030815.6531-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=lede-dev@lists.infradead.org \
--cc=openwrt@bitsofnetworks.org \
--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).