From: Sergei Trofimovich <slyich@gmail.com>
To: Jason Wang <jasowang@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Sergei Trofimovich <slyfox@gentoo.org>,
Glauber Costa <glommer@parallels.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCHv 2] tcp: properly initialize tcp memory limits part 2 (fix nfs regression)
Date: Fri, 2 Mar 2012 20:24:21 +0300 [thread overview]
Message-ID: <20120302202421.753b36bc@sf.home> (raw)
In-Reply-To: <4F509150.5060904@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2236 bytes --]
> > The change looks like a typo (division flipped to multiplication):
> >> limit = nr_free_buffer_pages() / 8;
> >> limit = nr_free_buffer_pages()<< (PAGE_SHIFT - 10);
>
> Hi, thanks for the reporting. It's not a typo. It was previously:
> sysctl_tcp_mem[1] << (PAGE_SHIFT - 7). Looks like we need to do the
> limit check before shift the value. Please try the following patch, thanks.
Still does not help. I test it by checking sha1sum of a large file over NFS
(small files seem to work simetimes):
$ strace sha1sum /gentoo/distfiles/gcc-4.6.2.tar.bz2
...
open("/gentoo/distfiles/gcc-4.6.2.tar.bz2", O_RDONLY
<HUNG>
After a certain timeout dmesg gets odd spam:
[ 314.848094] nfs: server vmhost not responding, still trying
[ 314.848134] nfs: server vmhost not responding, still trying
[ 314.848145] nfs: server vmhost not responding, still trying
[ 314.957047] nfs: server vmhost not responding, still trying
[ 314.957066] nfs: server vmhost not responding, still trying
[ 314.957075] nfs: server vmhost not responding, still trying
[ 314.957085] nfs: server vmhost not responding, still trying
[ 314.957100] nfs: server vmhost not responding, still trying
[ 314.958023] nfs: server vmhost not responding, still trying
[ 314.958035] nfs: server vmhost not responding, still trying
[ 314.958044] nfs: server vmhost not responding, still trying
[ 314.958054] nfs: server vmhost not responding, still trying
looks like bogus messages. Might be relevant to mishandled timings
somewhere else or a bug in nfs code.
> diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
> index 22ef5f9..4035aab 100644
> --- a/net/ipv4/tcp.c
> +++ b/net/ipv4/tcp.c
> @@ -3299,8 +3299,8 @@ void __init tcp_init(void)
>
> tcp_init_mem(&init_net);
> /* 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);
> + limit = nr_free_buffer_pages() / 8;
> + limit = max(limit, 128UL) << (PAGE_SHIFT - 7);
> max_share = min(4UL*1024*1024, limit);
>
> sysctl_tcp_wmem[0] = SK_MEM_QUANTUM;
>
>
>
--
Sergei
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-03-02 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 7:59 [PATCHv 2] tcp: properly initialize tcp memory limits part 2 (fix nfs regression) Sergei Trofimovich
2012-03-02 9:22 ` Jason Wang
2012-03-02 17:24 ` Sergei Trofimovich [this message]
2012-03-02 17:50 ` Sergei Trofimovich
2012-03-03 14:16 ` Glauber Costa
2012-03-03 14:43 ` Sergei Trofimovich
2012-03-03 23:27 ` Glauber Costa
2012-03-04 9:14 ` Sergei Trofimovich
2012-03-05 6:18 ` Jason Wang
2012-03-05 18:22 ` Sergei Trofimovich
2012-03-06 3:22 ` 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=20120302202421.753b36bc@sf.home \
--to=slyich@gmail.com \
--cc=davem@davemloft.net \
--cc=glommer@parallels.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=slyfox@gentoo.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;
as well as URLs for NNTP newsgroup(s).