From: Christian Schmid <webmaster@rapidforum.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com
Subject: Re: Bug-hunting
Date: Tue, 22 Feb 2005 20:17:55 +0100 [thread overview]
Message-ID: <421B8563.9030608@rapidforum.com> (raw)
In-Reply-To: <20050222104448.31373a99.davem@davemloft.net>
No. This is a new thing and this wasnt there before. In 2.6.10-rc2 the kernel aborted programs with
"Out of memory" when too many buffers are allocated and low memory was full. NOW it just shrinks the
buffers dynamically. I don't want that. I have a 2/2 system and I want 1600 MB for buffers but you
only allow around 700 MB for buffers. This is definetly NEW.
David S. Miller wrote:
> On Tue, 22 Feb 2005 16:07:35 +0100
> Christian Schmid <webmaster@rapidforum.com> wrote:
>
>
>>I am still trying to hunt down the bug with the slowdown-on-many-sockets. Is there any way I can see
>>how much tcp-memory is used right now? Why did you change the behaviour? In 2.6.10-rc2 I was able to
>>see the amount by looking in slabinfo but now the buffers are gone. And where did you introduce the
>>buffer-limit? It seems its now globally limited to xxx MB. I want to disable this in order to check
>>if thats the reason.
>
>
> The global TCP memory limit, controllable by sysctl()'s, has been there for
> at least 3 years.
>
>
next prev parent reply other threads:[~2005-02-22 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 15:07 Bug-hunting Christian Schmid
2005-02-22 18:44 ` Bug-hunting David S. Miller
2005-02-22 19:17 ` Christian Schmid [this message]
2005-02-22 19:51 ` Bug-hunting David S. Miller
2005-02-22 23:21 ` Bug-hunting Christian Schmid
2005-02-23 3:30 ` Bug-hunting David S. Miller
2005-02-23 10:28 ` Bug-hunting Christian Schmid
2005-02-23 19:29 ` Bug-hunting David S. Miller
2005-02-23 19:41 ` Bug-hunting Christian Schmid
2005-02-23 19:53 ` Bug-hunting David S. Miller
2005-02-23 19:46 ` Bug-hunting Christian Schmid
2005-02-23 20:00 ` Bug-hunting John Heffner
2005-02-24 12:29 ` Bug-hunting Christian Schmid
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=421B8563.9030608@rapidforum.com \
--to=webmaster@rapidforum.com \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.