From: Glauber Costa <glommer@parallels.com>
To: Jason Wang <jasowang@redhat.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<linux-kernel@vger.kernel.org>, <mst@redhat.com>
Subject: Re: [v3.3-rc2+ PATCH] tcp: properly initialize tcp memory limits
Date: Thu, 2 Feb 2012 14:39:26 +0400 [thread overview]
Message-ID: <4F2A67DE.1000909@parallels.com> (raw)
In-Reply-To: <20120202100700.38694.80000.stgit@amd-6168-8-1.englab.nay.redhat.com>
On 02/02/2012 02:07 PM, Jason Wang wrote:
> Commit 4acb4190 tries to fix the using uninitialized value
> introduced by commit 3dc43e3, but it would make the
> per-socket memory limits too small.
>
> This patch fixes this and also remove the redundant codes
> introduced in 4acb4190.
>
> Signed-off-by: Jason Wang<jasowang@redhat.com>
Acked-by: Glauber Costa <glommer@parallels.com>
> ---
> net/ipv4/sysctl_net_ipv4.c | 5 -----
> net/ipv4/tcp.c | 4 ++--
> 2 files changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/net/ipv4/sysctl_net_ipv4.c b/net/ipv4/sysctl_net_ipv4.c
> index 4cb9cd2..1eb8caa 100644
> --- a/net/ipv4/sysctl_net_ipv4.c
> +++ b/net/ipv4/sysctl_net_ipv4.c
> @@ -815,11 +815,6 @@ static __net_init int ipv4_sysctl_init_net(struct net *net)
> net->ipv4.sysctl_rt_cache_rebuild_count = 4;
>
> tcp_init_mem(net);
> - limit = nr_free_buffer_pages() / 8;
> - limit = max(limit, 128UL);
> - net->ipv4.sysctl_tcp_mem[0] = limit / 4 * 3;
> - net->ipv4.sysctl_tcp_mem[1] = limit;
> - net->ipv4.sysctl_tcp_mem[2] = net->ipv4.sysctl_tcp_mem[0] * 2;
>
> net->ipv4.ipv4_hdr = register_net_sysctl_table(net,
> net_ipv4_ctl_path, table);
Ok, this is indeed a good change, since we avoid initializing it twice.
> diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
> index 06373b4..3a7514b 100644
> --- a/net/ipv4/tcp.c
> +++ b/net/ipv4/tcp.c
> @@ -3218,7 +3218,6 @@ __setup("thash_entries=", set_thash_entries);
>
> void tcp_init_mem(struct net *net)
> {
> - /* Set per-socket limits to no more than 1/128 the pressure threshold */
> unsigned long limit = nr_free_buffer_pages() / 8;
> limit = max(limit, 128UL);
> net->ipv4.sysctl_tcp_mem[0] = limit / 4 * 3;
> @@ -3287,7 +3286,8 @@ void __init tcp_init(void)
> sysctl_max_syn_backlog = max(128, cnt / 256);
>
> tcp_init_mem(&init_net);
> - limit = nr_free_buffer_pages() / 8;
> + /* Set per-socket limits to no more than 1/128 the pressure threshold */
> + limit = nr_free_buffer_pages()<< (PAGE_SHIFT - 10);
> limit = max(limit, 128UL);
> max_share = min(4UL*1024*1024, limit);
Indeed, this ends up influencing the value of max_share used below to
initialize the other fields.
I like your change because now the limit variable is being set
independently between the global (now per-cgroup) and the per-socket
limits. (it previously was limit = sysctl_tcp_mem[1] << (PAGE_SHIFT-7))
So in the end, I personally think this is even clearer than what we had
before.
Acked-by: Glauber Costa <glommer@parallels.com>
next prev parent reply other threads:[~2012-02-02 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 10:07 [v3.3-rc2+ PATCH] tcp: properly initialize tcp memory limits Jason Wang
2012-02-02 10:39 ` Glauber Costa [this message]
2012-02-02 19:27 ` David Miller
2012-02-03 3:26 ` Jason Wang
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=4F2A67DE.1000909@parallels.com \
--to=glommer@parallels.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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