From: Holger Eitzenberger <holger@my-eitzenberger.de>
To: Andrew Morton <akpm@osdl.org>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org, stable@kernel.org,
torvalds@osdl.org, netdev@vger.kernel.org
Subject: Re: Linux 2.6.15.2
Date: Sat, 4 Feb 2006 12:52:17 +0100 [thread overview]
Message-ID: <20060204115217.GA5302@kruemel.my-eitzenberger.de> (raw)
In-Reply-To: <20060203111414.7026f46f.akpm@osdl.org>
On Fri, Feb 03, 2006 at 11:14:14AM -0800, Andrew Morton wrote:
> http://www.mail-archive.com/netdev@vger.kernel.org/msg06355.html
> > A look into /proc/sys/net/ipv4/tcp_mem showed that that the values in
> > there were way to high. I hope that a reduction of these values will
> > help (not done yet).
> Sounds different. Please test a more recent kernel and if the problem is
> still there, send a report to linux-kernel and cc netdev@vger.kernel.org.
> Include the contents of /proc/meminfo and /proc/slabinfo. Thanks.
I solved the issue.
Recent kernels have alloc_large_system_hash() exactly for that, and
tcp_init() uses it. It has nr_all_pages and nr_kernel_pages to
determine the actual size of usable RAM, whereas 2.6.10 just uses
num_physpages. That's the reason why the values in tcp_mem are way
too high on machines with 3-4 Gig RAM.
Thanks. /holger
--
ICQ 2882018 ++ Jabber: octavian@amessage.de ++
next prev parent reply other threads:[~2006-02-04 13:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 7:06 Greg KH
2006-01-31 7:07 ` Greg KH
2006-01-31 7:34 ` Andrew Morton
2006-01-31 7:38 ` Greg KH
2006-01-31 7:44 ` Andrew Morton
2006-01-31 17:43 ` Greg KH
2006-01-31 13:04 ` Steven Rostedt
2006-02-03 12:09 ` Holger Eitzenberger
2006-02-03 19:14 ` Andrew Morton
2006-02-04 11:52 ` Holger Eitzenberger [this message]
2006-01-31 14:31 Maciej Soltysiak
2006-02-07 15:55 ` Andrea Arcangeli
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=20060204115217.GA5302@kruemel.my-eitzenberger.de \
--to=holger@my-eitzenberger.de \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®