From: Andi Kleen <ak@suse.de>
To: Kumiko Ono <kumiko@cs.columbia.edu>
Cc: netdev@vger.kernel.org
Subject: Re: How can we make more use of memory for TCP properly?
Date: Wed, 14 Jun 2006 07:20:20 +0200 [thread overview]
Message-ID: <200606140720.20504.ak@suse.de> (raw)
In-Reply-To: <448F323A.7000005@cs.columbia.edu>
> Accorting to TCP man page, the kernel calculates the values of
> sysctl_tcp_mem depending on available physical memory at boot time.
> I added 2GB RAM to a machine that had 2GB, and then it has 4GB RAM now.
> However, the value of sysctl_tcp_mem[2] has not changed from 196608
> (pages). The machine is running at Linux 2.6.16.5 i686 Intel(R)
> Pentium(R) 4 CPU 3.06GHz.
TCP can only use low memory for this which is limited to around 900MB
on 32bit systems. 64bit CPUs don't have this problem.
-Andi
prev parent reply other threads:[~2006-06-14 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 21:46 How can we make more use of memory for TCP properly? Kumiko Ono
2006-06-14 5:20 ` Andi Kleen [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=200606140720.20504.ak@suse.de \
--to=ak@suse.de \
--cc=kumiko@cs.columbia.edu \
--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;
as well as URLs for NNTP newsgroup(s).