Netdev Archive on lore.kernel.org help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com> To: Paolo Abeni <pabeni@redhat.com>, netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org> Cc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>, David Ahern <dsahern@kernel.org>, Eric Dumazet <edumazet@google.com>, Willem de Bruijn <willemdebruijn.kernel@gmail.com>, linux-kernel@vger.kernel.org Subject: Re: [PATCH 09/14] ipv6: hand dst refs to cork setup Date: Tue, 11 Jan 2022 20:39:26 +0000 [thread overview] Message-ID: <9e3bb558-ecb1-a6aa-35e4-a2771136b3fe@gmail.com> (raw) In-Reply-To: <48293134f179d643e9ec7bcbd7bca895df7611ac.camel@redhat.com> On 1/11/22 17:11, Paolo Abeni wrote: > On Tue, 2022-01-11 at 01:21 +0000, Pavel Begunkov wrote: >> During cork->dst setup, ip6_make_skb() gets an additional reference to >> a passed in dst. However, udpv6_sendmsg() doesn't need dst after calling >> ip6_make_skb(), and so we can save two additional atomics by passing >> dst references to ip6_make_skb(). udpv6_sendmsg() is the only caller, so >> it's enough to make sure it doesn't use dst afterwards. > > What about the corked path in udp6_sendmsg()? I mean: It doesn't change it for callers, so the ref stays with udp6_sendmsg() when corking. To compensate for ip6_setup_cork() there is an explicit dst_hold() in ip6_append_data, should be fine. @@ -1784,6 +1784,7 @@ int ip6_append_data(struct sock *sk, /* * setup for corking */ + dst_hold(&rt->dst); err = ip6_setup_cork(sk, &inet->cork, &np->cork, ipc6, rt); I don't care much about corking perf, but might be better to implement this "handing away" for ip6_append_data() as well to be more consistent with ip6_make_skb(). > udp6_sendmsg(MSG_MORE) -> ip6_append_data() -> ip6_setup_cork() > > what if ip6_setup_cork() errors out in that path? -- Pavel Begunkov
next prev parent reply other threads:[~2022-01-11 20:42 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-11 1:21 [PATCH 00/14] udp optimisation Pavel Begunkov 2022-01-11 1:21 ` [PATCH 01/14] ipv6: optimise dst referencing Pavel Begunkov 2022-01-11 1:21 ` [PATCH 02/14] ipv6: shuffle up->pending AF_INET bits Pavel Begunkov 2022-01-11 1:21 ` [PATCH 03/14] ipv6: remove daddr temp buffer in __ip6_make_skb Pavel Begunkov 2022-01-11 1:21 ` [PATCH 04/14] ipv6: clean up cork setup/release Pavel Begunkov 2022-01-11 1:21 ` [PATCH 05/14] ipv6: don't zero cork's flowi after use Pavel Begunkov 2022-01-11 1:21 ` [PATCH 06/14] ipv6: pass full cork into __ip6_append_data() Pavel Begunkov 2022-01-11 1:21 ` [PATCH 07/14] ipv6: pass flow in ip6_make_skb together with cork Pavel Begunkov 2022-01-11 1:21 ` [PATCH 08/14] ipv6/udp: don't make extra copies of iflow Pavel Begunkov 2022-01-11 1:21 ` [PATCH 09/14] ipv6: hand dst refs to cork setup Pavel Begunkov 2022-01-11 15:39 ` Willem de Bruijn 2022-01-11 15:57 ` Pavel Begunkov 2022-01-11 17:11 ` Paolo Abeni 2022-01-11 20:39 ` Pavel Begunkov [this message] 2022-01-12 11:15 ` Paolo Abeni 2022-01-12 16:49 ` Pavel Begunkov 2022-01-11 1:21 ` [PATCH 10/14] skbuff: drop zero check from skb_zcopy_set Pavel Begunkov 2022-01-11 1:21 ` [PATCH 11/14] skbuff: drop null check from skb_zcopy Pavel Begunkov 2022-01-11 1:21 ` [PATCH 12/14] skbuff: optimise alloc_skb_with_frags() Pavel Begunkov 2022-01-11 1:21 ` [PATCH 13/14] net: inline part of skb_csum_hwoffload_help Pavel Begunkov 2022-01-11 9:24 ` David Laight 2022-01-11 16:59 ` Pavel Begunkov 2022-01-11 17:25 ` David Laight 2022-01-11 20:48 ` Pavel Begunkov 2022-01-12 2:41 ` David Laight 2022-01-12 16:43 ` Pavel Begunkov 2022-01-11 1:21 ` [PATCH 14/14] net: inline sock_alloc_send_skb Pavel Begunkov
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=9e3bb558-ecb1-a6aa-35e4-a2771136b3fe@gmail.com \ --to=asml.silence@gmail.com \ --cc=davem@davemloft.net \ --cc=dsahern@kernel.org \ --cc=edumazet@google.com \ --cc=kuba@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=pabeni@redhat.com \ --cc=willemdebruijn.kernel@gmail.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: linkBe 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; as well as URLs for NNTP newsgroup(s).