aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/drivers/net/wireguard/peer.h
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2021-06-04 17:17:34 +0200
committerDavid S. Miller <davem@davemloft.net>2021-06-04 14:25:14 -0700
commita4e9f8e3287c9eb6bf70df982870980dd3341863 (patch)
treed1b7068678c63f49dfec3df2ebe0570c9777baeb /drivers/net/wireguard/peer.h
parentwireguard: use synchronize_net rather than synchronize_rcu (diff)
downloadwireguard-linux-a4e9f8e3287c9eb6bf70df982870980dd3341863.tar.xz
wireguard-linux-a4e9f8e3287c9eb6bf70df982870980dd3341863.zip
wireguard: peer: allocate in kmem_cache
With deployments having upwards of 600k peers now, this somewhat heavy structure could benefit from more fine-grained allocations. Specifically, instead of using a 2048-byte slab for a 1544-byte object, we can now use 1544-byte objects directly, thus saving almost 25% per-peer, or with 600k peers, that's a savings of 303 MiB. This also makes wireguard's memory usage more transparent in tools like slabtop and /proc/slabinfo. Fixes: 8b5553ace83c ("wireguard: queueing: get rid of per-peer ring buffers") Suggested-by: Arnd Bergmann <arnd@arndb.de> Suggested-by: Matthew Wilcox <willy@infradead.org> Cc: stable@vger.kernel.org Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '')
-rw-r--r--drivers/net/wireguard/peer.h3
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/net/wireguard/peer.h b/drivers/net/wireguard/peer.h
index 8d53b687a1d1..76e4d3128ad4 100644
--- a/drivers/net/wireguard/peer.h
+++ b/drivers/net/wireguard/peer.h
@@ -80,4 +80,7 @@ void wg_peer_put(struct wg_peer *peer);
void wg_peer_remove(struct wg_peer *peer);
void wg_peer_remove_all(struct wg_device *wg);
+int wg_peer_init(void);
+void wg_peer_uninit(void);
+
#endif /* _WG_PEER_H */