From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: brouer@redhat.com, davem@davemloft.net, netdev@vger.kernel.org,
willemb@google.com, eric.dumazet@gmail.com, dsahern@gmail.com,
yoshfuji@linux-ipv6.org, Dave Jones <dsj@fb.com>
Subject: Re: [PATCH net-next v3] net: ip: avoid OOM kills with large UDP sends over loopback
Date: Wed, 23 Jun 2021 21:45:55 +0200 [thread overview]
Message-ID: <20210623214555.5c683821@carbon> (raw)
In-Reply-To: <20210623162328.2197645-1-kuba@kernel.org>
On Wed, 23 Jun 2021 09:23:28 -0700
Jakub Kicinski <kuba@kernel.org> wrote:
> Dave observed number of machines hitting OOM on the UDP send
> path. The workload seems to be sending large UDP packets over
> loopback. Since loopback has MTU of 64k kernel will try to
> allocate an skb with up to 64k of head space. This has a good
> chance of failing under memory pressure. What's worse if
> the message length is <32k the allocation may trigger an
> OOM killer.
>
> This is entirely avoidable, we can use an skb with page frags.
>
> af_unix solves a similar problem by limiting the head
> length to SKB_MAX_ALLOC. This seems like a good and simple
> approach. It means that UDP messages > 16kB will now
> use fragments if underlying device supports SG, if extra
> allocator pressure causes regressions in real workloads
> we can switch to trying the large allocation first and
> falling back.
>
> Reported-by: Dave Jones <dsj@fb.com>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> net/ipv4/ip_output.c | 4 +++-
> net/ipv6/ip6_output.c | 4 +++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/net/ipv4/ip_output.c b/net/ipv4/ip_output.c
> index c3efc7d658f6..790dd28fd198 100644
> --- a/net/ipv4/ip_output.c
> +++ b/net/ipv4/ip_output.c
> @@ -1077,7 +1077,9 @@ static int __ip_append_data(struct sock *sk,
> if ((flags & MSG_MORE) &&
> !(rt->dst.dev->features&NETIF_F_SG))
> alloclen = mtu;
> - else if (!paged)
> + else if (!paged &&
> + (fraglen + hh_len + 15 < SKB_MAX_ALLOC ||
What does the number 15 represent here?
> + !(rt->dst.dev->features & NETIF_F_SG)))
> alloclen = fraglen;
> else {
> alloclen = min_t(int, fraglen, MAX_HEADER);
> diff --git a/net/ipv6/ip6_output.c b/net/ipv6/ip6_output.c
> index ff4f9ebcf7f6..ae8dbd6cdab1 100644
> --- a/net/ipv6/ip6_output.c
> +++ b/net/ipv6/ip6_output.c
> @@ -1585,7 +1585,9 @@ static int __ip6_append_data(struct sock *sk,
> if ((flags & MSG_MORE) &&
> !(rt->dst.dev->features&NETIF_F_SG))
> alloclen = mtu;
> - else if (!paged)
> + else if (!paged &&
> + (fraglen + hh_len < SKB_MAX_ALLOC ||
The number 15 is not use here.
> + !(rt->dst.dev->features & NETIF_F_SG)))
> alloclen = fraglen;
> else {
> alloclen = min_t(int, fraglen, MAX_HEADER);
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2021-06-23 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 16:23 [PATCH net-next v3] net: ip: avoid OOM kills with large UDP sends over loopback Jakub Kicinski
2021-06-23 18:05 ` Eric Dumazet
2021-06-23 18:11 ` Eric Dumazet
2021-06-23 19:45 ` Jesper Dangaard Brouer [this message]
2021-06-23 21:07 ` Jakub Kicinski
2021-06-24 2:23 ` Willem de Bruijn
2021-06-23 21:14 ` Eric Dumazet
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=20210623214555.5c683821@carbon \
--to=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dsj@fb.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
--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