summaryrefslogtreecommitdiff
path: root/drivers/net/wireguard/selftest/allowedips.c
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
commitb284d5a787433ec50a222ebcceed6256f4ca3274 (patch)
tree0dff87ccd3707ab64fbf9f84f94bc2bd5f4c9cf7 /drivers/net/wireguard/selftest/allowedips.c
parent5a104dcd5da919cb1e6690be5084f61dd2b57c85 (diff)
downloadwireguard-linux-trimmed-b284d5a787433ec50a222ebcceed6256f4ca3274.tar.gz
wireguard-linux-trimmed-b284d5a787433ec50a222ebcceed6256f4ca3274.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: b955554b47af ("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 'drivers/net/wireguard/selftest/allowedips.c')
0 files changed, 0 insertions, 0 deletions