mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ville Herva <vherva@niksula.hut.fi>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Samuli Suonpaa <suonpaa@iki.fi>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.16: Out of memory - when still more than 100MB free
Date: Tue, 18 Dec 2001 14:18:58 +0200	[thread overview]
Message-ID: <20011218141858.O12063@niksula.cs.hut.fi> (raw)
In-Reply-To: <87elltwmgz.fsf@puck.erasmus.jurri.net> <Pine.LNX.4.21.0112171909320.3767-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0112171909320.3767-100000@freak.distro.conectiva>; from marcelo@conectiva.com.br on Mon, Dec 17, 2001 at 07:10:54PM -0200

On Mon, Dec 17, 2001 at 07:10:54PM -0200, you [Marcelo Tosatti] claimed:
> 
> 
> On 17 Dec 2001, Samuli Suonpaa wrote:
> 
> > I've got VMWare killed a couple of times mysteriously. 
> > 
> > I've got 256MB memory and no swap on my laptop running 2.4.16 and for
> > some reason VMWare has got killed with the following syslog
> > information:
> > 
> > Dec 17 23:33:23 puck kernel: Out of Memory: Killed process 28803 (vmware).
> > Dec 17 23:33:35 puck kernel: Out of Memory: Killed process 28804 (vmware).
> > Dec 17 23:33:37 puck kernel: /dev/vmmon: Vmx86_ReleaseVM: unlocked pages: 75286, unlocked dirty pages: 51084
> 
> Samuli, 
> 
> The problem is that buffer/cache/{i,d}cache pages are not getting freed
> easily, and instead the kernel swapouts anonymous memory.
> 
> Could you please try 2.4.17-rc1 and tell me if it makes a difference for
> you ? 

See my report on what happens on a 2GB box with .16 or .17rc1. Buffers are
still not released as they should.

http://marc.theaimsgroup.com/?l=linux-kernel&m=100849985518543&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=100857274818037&w=2

Perhaps someone could test on x86 with less memory (I can do that later, but
right now I don't have any throw-away box with a recent kernel on it). On ia64
with 2GB+256MB swap this results in OOM when trying to allocate and use
1.7GB, albeit the real mem usage (-buffers) is less than 200MB. 

Basically the test is

fill cache 

 find / -type f -exec cat {} \; > /dev/null
 updatedb     

then run this with suitable argument:

#include <stdio.h>
#include <stdlib.h>

#define BKSP "\010\010\010\010\010\010"

int main(int argc, char** argv)
{
    unsigned long megs = 512;
    unsigned long size, i;
    unsigned char* buf;
    if (argc > 1) megs = atol(argv[1]);
    size = megs * 1024 * 1024;
    
    fprintf(stderr, "Allocating %lu megs...\n\n      ", megs);
    buf = malloc(size);
    if (!buf)
    {
         fprintf(stderr, "malloc(%lu", size);
         perror(")");
         exit(-1);
    }
    
    for (i = 0; i < size; i++)
    {
         buf[i] = 42;
         
         if ((i + 1) % (1024 * 1024) == 0) 
             fprintf(stderr, BKSP "%4uMB", (i + 1) / 1024 / 1024);
    }
    
    fprintf(stderr, "\n Success.\n");
    
    return 1;
}


-- v --

v@iki.fi

  reply	other threads:[~2001-12-18 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-17 21:44 Samuli Suonpaa
2001-12-17 21:10 ` Marcelo Tosatti
2001-12-18 12:18   ` Ville Herva [this message]
2001-12-17 22:54 Steve Kieu

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=20011218141858.O12063@niksula.cs.hut.fi \
    --to=vherva@niksula.hut.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=suonpaa@iki.fi \
    /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®