mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mukesh agrawal <m.lkml@agrawals.org>
To: Michael May <michael.may@tnt.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Memory
Date: Fri, 1 Feb 2002 21:48:44 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0202012143220.32631-100000@take2.> (raw)
In-Reply-To: <200201301648.g0UGmtj32611@pcchk.intra.tnt.de>


> Hi folks,
>
>
> I think there is a little Problem with Kernel 2.4.17-pre4 - pre7
>
> When the machine in up for longer than 2 days and is under higher load, the processes will killed, with some syslog-messages:
>
> kernel: Out of memory: Killed process <pid>
>
> I don't know what the Problem is, and all machines where it is, are SMP-Machines on i386.
>
> Two times, I traced the problem and the system reported full memory.
> But, the processes and the Utilities are the same like before updating the kernel,
> except the gcc (is now 3.0.3)

If this is the same problem that I'm seeing, what's happening is that the
buffer and cache memory (as reported in top) is not being freed early
enough.

In my situation, what happens is that (over time), buffers+cache grows to
80MB or more (out of 320MB total available; no swap). Factoring in the
memory used by running processes, the uncommitted memory falls to <10MB.
Then, when Mozilla or StarOffice tries to allocate some more memory, the
OOM killer picks one of them instead of shrinking the cache.

I'd check the amount of memory allocated to buffers and cache after one
your OOM events and see if that explains why you're now seeing low memory
conditions with the same workload.



      parent reply	other threads:[~2002-02-02  2:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 16:48 Michael May
2002-01-30 18:03 ` Alan Cox
2002-02-02  2:48 ` mukesh agrawal [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=Pine.LNX.4.44.0202012143220.32631-100000@take2. \
    --to=m.lkml@agrawals.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.may@tnt.de \
    /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®