summaryrefslogtreecommitdiff
path: root/drivers/net/wireguard/selftest
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2021-06-04 17:17:37 +0200
committerDavid S. Miller <davem@davemloft.net>2021-06-04 14:25:14 -0700
commit624b07f8bac33565f9e081d9abb8b81994577bcd (patch)
tree43d574b4f3d76df014b3589a81749cbd1dbbe073 /drivers/net/wireguard/selftest
parentb019d02e03623372f784f2eb3ac76bfcf379e21e (diff)
downloadwireguard-linux-trimmed-624b07f8bac33565f9e081d9abb8b81994577bcd.tar.gz
wireguard-linux-trimmed-624b07f8bac33565f9e081d9abb8b81994577bcd.zip
wireguard: allowedips: allocate nodes in kmem_cache
The previous commit moved from O(n) to O(1) for removal, but in the process introduced an additional pointer member to a struct that increased the size from 60 to 68 bytes, putting nodes in the 128-byte slab. With deployed systems having as many as 2 million nodes, this represents a significant doubling in memory usage (128 MiB -> 256 MiB). Fix this by using our own kmem_cache, that's sized exactly right. This also makes wireguard's memory usage more transparent in tools like slabtop and /proc/slabinfo. Fixes: a8f1bc7bdea3 ("net: WireGuard secure network tunnel") 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')
0 files changed, 0 insertions, 0 deletions