From: Paolo Abeni <pabeni@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
James Morris <jmorris@namei.org>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Alexander Duyck <aduyck@mirantis.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Eric Dumazet <edumazet@google.com>,
Tom Herbert <tom@herbertland.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Edward Cree <ecree@solarflare.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH net-next v2 3/3] udp: use it's own memory accounting schema
Date: Wed, 28 Sep 2016 09:43:33 +0200 [thread overview]
Message-ID: <1475048613.4693.1.camel@redhat.com> (raw)
In-Reply-To: <1475001734.28155.62.camel@edumazet-glaptop3.roam.corp.google.com>
On Tue, 2016-09-27 at 11:42 -0700, Eric Dumazet wrote:
> On Tue, 2016-09-27 at 18:58 +0200, Paolo Abeni wrote:
>
>
> >
> > Since the new memory accounting model does not require socket
> > locking, remove the lock on enqueue and free and avoid using the
> > backlog on enqueue.
>
>
> ...
>
> > __UDP_INC_STATS(sock_net(sk), UDP_MIB_CSUMERRORS, is_udplite);
> > @@ -2345,6 +2325,7 @@ struct proto udp_prot = {
> > .connect = ip4_datagram_connect,
> > .disconnect = udp_disconnect,
> > .ioctl = udp_ioctl,
> > + .init = udp_init_sock,
> > .destroy = udp_destroy_sock,
> > .setsockopt = udp_setsockopt,
> > .getsockopt = udp_getsockopt,
> > @@ -2357,7 +2338,10 @@ struct proto udp_prot = {
> > .unhash = udp_lib_unhash,
> > .rehash = udp_v4_rehash,
> > .get_port = udp_v4_get_port,
> > + .enter_memory_pressure = udp_enter_memory_pressure,
> > + .sockets_allocated = &udp_sockets_allocated,
> > .memory_allocated = &udp_memory_allocated,
> > + .memory_pressure = &udp_memory_pressure,
> > .sysctl_mem = sysctl_udp_mem,
> > .sysctl_wmem = &sysctl_udp_wmem_min,
> > .sysctl_rmem = &sysctl_udp_rmem_min,
>
>
> I find disturbing you did not remove
>
> .backlog_rcv = __udp_queue_rcv_skb,
oops, left-over. I'll remove it in v3.
Thank you for pointing it out,
Paolo
prev parent reply other threads:[~2016-09-28 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 16:57 [PATCH net-next v2 0/3] udp: refactor memory accounting Paolo Abeni
2016-09-27 16:58 ` [PATCH net-next v2 2/3] udp: implement memory accounting helpers Paolo Abeni
[not found] ` <cover.1474995024.git.pabeni-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-27 16:58 ` [PATCH net-next v2 1/3] net/socket: factor out helpers for memory and queue manipulation Paolo Abeni
2016-09-27 16:58 ` [PATCH net-next v2 3/3] udp: use it's own memory accounting schema Paolo Abeni
[not found] ` <bc55b0885e0f93895c211168561a6b3403bade10.1474995024.git.pabeni-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-27 18:42 ` Eric Dumazet
2016-09-28 7:43 ` Paolo Abeni [this message]
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=1475048613.4693.1.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=aduyck@mirantis.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=jmorris@namei.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.com \
--cc=trond.myklebust@primarydata.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).