From: David Ahern <dsahern@kernel.org>
To: Jon Maxwell <jmaxwell37@gmail.com>, davem@davemloft.net
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
yoshfuji@linux-ipv6.org, martin.lau@kernel.org,
joel@joelfernandes.org, paulmck@kernel.org,
eyal.birger@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andrea Mayer <andrea.mayer@uniroma2.it>
Subject: Re: [net-next v2] ipv6: remove max_size check inline with ipv4
Date: Thu, 12 Jan 2023 21:03:55 -0700 [thread overview]
Message-ID: <e224073d-4c92-9a11-5385-4c38b06e6d15@kernel.org> (raw)
In-Reply-To: <20230112012532.311021-1-jmaxwell37@gmail.com>
On 1/11/23 6:25 PM, Jon Maxwell wrote:
> v2: Correct syntax error in net/ipv6/route.c
>
> In ip6_dst_gc() replace:
>
> if (entries > gc_thresh)
>
> With:
>
> if (entries > ops->gc_thresh)
>
> Sending Ipv6 packets in a loop via a raw socket triggers an issue where a
> route is cloned by ip6_rt_cache_alloc() for each packet sent. This quickly
> consumes the Ipv6 max_size threshold which defaults to 4096 resulting in
> these warnings:
>
> [1] 99.187805] dst_alloc: 7728 callbacks suppressed
> [2] Route cache is full: consider increasing sysctl net.ipv6.route.max_size.
> .
> .
> [300] Route cache is full: consider increasing sysctl net.ipv6.route.max_size.
>
> When this happens the packet is dropped and sendto() gets a network is
> unreachable error:
>
> # ./a.out -s
>
> remaining pkt 200557 errno 101
> remaining pkt 196462 errno 101
> .
> .
> remaining pkt 126821 errno 101
>
> Implement David Aherns suggestion to remove max_size check seeing that Ipv6
> has a GC to manage memory usage. Ipv4 already does not check max_size.
>
> Here are some memory comparisons for Ipv4 vs Ipv6 with the patch:
>
> Test by running 5 instances of a program that sends UDP packets to a raw
> socket 5000000 times. Compare Ipv4 and Ipv6 performance with a similar
> program.
>
> Ipv4:
>
> Before test:
>
> # grep -e Slab -e Free /proc/meminfo
> MemFree: 29427108 kB
> Slab: 237612 kB
>
> # grep dst_cache /proc/slabinfo
> ip6_dst_cache 1912 2528 256 32 2 : tunables 0 0 0
> xfrm_dst_cache 0 0 320 25 2 : tunables 0 0 0
> ip_dst_cache 2881 3990 192 42 2 : tunables 0 0 0
>
> During test:
>
> # grep -e Slab -e Free /proc/meminfo
> MemFree: 29417608 kB
> Slab: 247712 kB
>
> # grep dst_cache /proc/slabinfo
> ip6_dst_cache 1912 2528 256 32 2 : tunables 0 0 0
> xfrm_dst_cache 0 0 320 25 2 : tunables 0 0 0
> ip_dst_cache 44394 44394 192 42 2 : tunables 0 0 0
>
> After test:
>
> # grep -e Slab -e Free /proc/meminfo
> MemFree: 29422308 kB
> Slab: 238104 kB
>
> # grep dst_cache /proc/slabinfo
> ip6_dst_cache 1912 2528 256 32 2 : tunables 0 0 0
> xfrm_dst_cache 0 0 320 25 2 : tunables 0 0 0
> ip_dst_cache 3048 4116 192 42 2 : tunables 0 0 0
>
> Ipv6 with patch:
>
> Errno 101 errors are not observed anymore with the patch.
>
> Before test:
>
> # grep -e Slab -e Free /proc/meminfo
> MemFree: 29422308 kB
> Slab: 238104 kB
>
> # grep dst_cache /proc/slabinfo
> ip6_dst_cache 1912 2528 256 32 2 : tunables 0 0 0
> xfrm_dst_cache 0 0 320 25 2 : tunables 0 0 0
> ip_dst_cache 3048 4116 192 42 2 : tunables 0 0 0
>
> During Test:
>
> # grep -e Slab -e Free /proc/meminfo
> MemFree: 29431516 kB
> Slab: 240940 kB
>
> # grep dst_cache /proc/slabinfo
> ip6_dst_cache 11980 12064 256 32 2 : tunables 0 0 0
> xfrm_dst_cache 0 0 320 25 2 : tunables 0 0 0
> ip_dst_cache 3048 4116 192 42 2 : tunables 0 0 0
>
> After Test:
>
> # grep -e Slab -e Free /proc/meminfo
> MemFree: 29441816 kB
> Slab: 238132 kB
>
> # grep dst_cache /proc/slabinfo
> ip6_dst_cache 1902 2432 256 32 2 : tunables 0 0 0
> xfrm_dst_cache 0 0 320 25 2 : tunables 0 0 0
> ip_dst_cache 3048 4116 192 42 2 : tunables 0 0 0
>
> Tested-by: Andrea Mayer <andrea.mayer@uniroma2.it>
> Signed-off-by: Jon Maxwell <jmaxwell37@gmail.com>
> ---
> include/net/dst_ops.h | 2 +-
> net/core/dst.c | 8 ++------
> net/ipv6/route.c | 13 +++++--------
> 3 files changed, 8 insertions(+), 15 deletions(-)
>
Thanks for the data in the commit message.
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2023-01-13 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 1:25 Jon Maxwell
2023-01-12 20:41 ` Andrea Mayer
2023-01-12 21:48 ` Jonathan Maxwell
2023-01-12 22:26 ` Andrea Mayer
2023-01-13 4:03 ` David Ahern [this message]
2023-01-14 5:40 ` patchwork-bot+netdevbpf
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=e224073d-4c92-9a11-5385-4c38b06e6d15@kernel.org \
--to=dsahern@kernel.org \
--cc=andrea.mayer@uniroma2.it \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eyal.birger@gmail.com \
--cc=jmaxwell37@gmail.com \
--cc=joel@joelfernandes.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/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
all inboxes | Powered by JetHome®