From: Paolo Abeni <pabeni@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Network Development <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Willem de Bruijn <willemb@google.com>,
steffen.klassert@secunet.com,
Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Subject: Re: [RFC PATCH v3 01/10] udp: implement complete book-keeping for encap_needed
Date: Fri, 02 Nov 2018 14:30:52 +0100 [thread overview]
Message-ID: <889289db760143421dd097bf0ea1c5e6a15f1df7.camel@redhat.com> (raw)
In-Reply-To: <CAF=yD-KMU9+UvL-UNFnZth31O+NzGzdqFHNCq-QbSpZ4_qY86A@mail.gmail.com>
Hi,
On Thu, 2018-11-01 at 16:59 -0400, Willem de Bruijn wrote:
> On Tue, Oct 30, 2018 at 1:28 PM Paolo Abeni <pabeni@redhat.com> wrote:
> >
> > The *encap_needed static keys are enabled by UDP tunnels
> > and several UDP encapsulations type, but they are never
> > turned off. This can cause unneeded overall performance
> > degradation for systems where such features are used
> > transiently.
> >
> > This patch introduces complete book-keeping for such keys,
> > decreasing the usage at socket destruction time, if needed,
> > and avoiding that the same socket could increase the key
> > usage multiple times.
> >
> > rfc v2 - rfc v3:
> > - use udp_tunnel_encap_enable() in setsockopt()
> >
> > Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> > @@ -2447,7 +2452,7 @@ int udp_lib_setsockopt(struct sock *sk, int level, int optname,
> > /* FALLTHROUGH */
> > case UDP_ENCAP_L2TPINUDP:
> > up->encap_type = val;
> > - udp_encap_enable();
> > + udp_tunnel_encap_enable(sk->sk_socket);
>
> this now also needs lock_sock?
Yep, you are right. I'll add it in the next iteration.
Thanks,
Paolo
next prev parent reply other threads:[~2018-11-02 22:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 17:24 [RFC PATCH v3 00/10] udp: implement GRO support Paolo Abeni
2018-10-30 17:24 ` [RFC PATCH v3 01/10] udp: implement complete book-keeping for encap_needed Paolo Abeni
2018-11-01 20:59 ` Willem de Bruijn
2018-11-02 13:30 ` Paolo Abeni [this message]
2018-10-30 17:24 ` [RFC PATCH v3 02/10] udp: implement GRO for plain UDP sockets Paolo Abeni
2018-10-30 17:24 ` [RFC PATCH v3 03/10] udp: add support for UDP_GRO cmsg Paolo Abeni
2018-10-30 17:24 ` [RFC PATCH v3 04/10] ip: factor out protocol delivery helper Paolo Abeni
2018-11-01 6:35 ` Subash Abhinov Kasiviswanathan
2018-11-02 13:30 ` Paolo Abeni
2018-10-30 17:24 ` [RFC PATCH v3 05/10] ipv6: " Paolo Abeni
2018-10-30 17:24 ` [RFC PATCH v3 06/10] udp: cope with UDP GRO packet misdirection Paolo Abeni
2018-10-31 9:54 ` Paolo Abeni
2018-11-01 21:01 ` Willem de Bruijn
2018-11-02 13:44 ` Paolo Abeni
2018-10-30 17:24 ` [RFC PATCH v3 07/10] selftests: add GRO support to udp bench rx program Paolo Abeni
2018-10-30 17:24 ` [RFC PATCH v3 08/10] selftests: conditionally enable XDP support in udpgso_bench_rx Paolo Abeni
2018-11-01 21:00 ` Willem de Bruijn
2018-10-30 17:24 ` [RFC PATCH v3 09/10] selftests: add some benchmark for UDP GRO Paolo Abeni
2018-10-30 17:24 ` [RFC PATCH v3 10/10] selftests: add functionals test " Paolo Abeni
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=889289db760143421dd097bf0ea1c5e6a15f1df7.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=subashab@codeaurora.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).