mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Holger Eitzenberger <holger@my-eitzenberger.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, stable@kernel.org,
	torvalds@osdl.org
Subject: Re: Linux 2.6.15.2
Date: Fri, 3 Feb 2006 13:09:25 +0100	[thread overview]
Message-ID: <20060203120925.GA4393@kruemel.my-eitzenberger.de> (raw)
In-Reply-To: <20060130233427.5e7912ae.akpm@osdl.org>

On Mon, Jan 30, 2006 at 11:34:27PM -0800, Andrew Morton wrote:

> - A skbuff_head_cache leak causes oom-killings.
> 
> All of these only seem to affect a small minority of machines.

Hi,

I have searched for a description for the above mentioned bug report,
but havent found any.  Can you tell me?

The reason why I am asking that I am facing a similar problem on
kernel 2.6.10.  During performance tests (Intel XEON, SMP, PCI-X,
e1000, 2 - 4 Gig RAM) the machine was out of memory.

Tests showed that LowFree went linearly down to a few megabytes, where
most of the memory was used in skb_head_cache and size-1024 slab
caches.  These two summed up to ~270 MG, which was the reason for
that.

/proc/net/tcp showed that most of the memory was stuck in the RX
queues of some processes (two processes with ~1000 sockets each).

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).

/holger

-- 
ICQ 2882018 ++ Jabber: octavian@amessage.de ++

  parent reply	other threads:[~2006-02-03 12:36 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 [this message]
2006-02-03 19:14     ` Andrew Morton
2006-02-04 11:52       ` Holger Eitzenberger
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=20060203120925.GA4393@kruemel.my-eitzenberger.de \
    --to=holger@my-eitzenberger.de \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@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®