public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Volkoff <vdb@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: Memory management in Kernel 2.4.x
Date: Tue, 28 May 2002 18:46:43 +0400	[thread overview]
Message-ID: <20020528184643.A796@localhost> (raw)

Hello,

> Unfortunately, the memory management of kernel 2.4.x didn't get better until 
> today. It is very easy to make a machine dead. Take the following script: 
> 
> http://groups.google.com/groups?q=malloc+bestie&hl=de&lr=&selm=slrn8aiglm.tqd.pfk@c.zeiss.de&rnum=2 
> 
> The result with kernel 2.4.19pre8ac4: 

What about results with latest -aa kernels? 
I'm writing this letter while running your killer-test ;)
My machine is perfectly responsive.

$ uname -a
Linux localhost 2.4.19-pre6vm33 #2 Sat Apr 13 00:56:55 MSD 2002 i686 unknown
This is vanilla 2.4.19-pre6 + vm33 from Andrea Arcangelly.

Funny stats:

bash-2.05$ free
total       used       free     shared    buffers     cached
Mem:        516496     512804       3692          0       2080      10064
-/+ buffers/cache:     500660      15836
Swap:      1028120    1028120          0

I'm running X, netscape, mutt, top, 5 xterms, web, mysql, ftp, samba etc.
Lots of "0-order allocation failed" in the log. Anyway it is usable!
The good thing is VM is killing right process most of the time: 

VM: killing process memory-killer

Netscape got killed. Big deal, I can start it again and it works... 

P.S. Running it already for 20 minutes.

-- 

    DV

             reply	other threads:[~2002-05-28 14:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 14:46 Dmitry Volkoff [this message]
     [not found] <fa.n12rl6v.9644rg@ifi.uio.no>
     [not found] ` <fa.jd9c9pv.190gl8n@ifi.uio.no>
2002-05-28  5:42   ` Memory management in Kernel 2.4.x Andreas Hartmann
2002-05-28 11:49     ` Alan Cox
2002-05-28 18:14       ` Andreas Hartmann
     [not found] <fa.iklie8v.5k2hbj@ifi.uio.no>
     [not found] ` <fa.na0lviv.e2a93a@ifi.uio.no>
2002-05-27 12:58   ` Andreas Hartmann
2002-05-27 13:45     ` Peter Wächtler
2002-05-27 15:25       ` Alan Cox
2002-05-27 14:37         ` Peter Wächtler
2002-05-27 21:22         ` H. Peter Anvin
2002-05-27 21:33           ` Benjamin LaHaise
2002-05-27 21:34             ` H. Peter Anvin
2002-05-27 21:37               ` Benjamin LaHaise
2002-05-27 21:39                 ` H. Peter Anvin
2002-05-27 22:50             ` Alan Cox
2002-05-27 21:56               ` William Lee Irwin III
2002-05-27 23:07                 ` Alan Cox
2002-05-27 22:48           ` Alan Cox
2002-06-05 13:33             ` Bill Davidsen
2002-05-31 21:19       ` Andrea Arcangeli
2002-06-01 12:35         ` Andreas Hartmann
2002-06-01 22:59           ` Andrea Arcangeli
2002-06-01 13:12         ` Andreas Hartmann
2002-06-03  8:11         ` Peter Wächtler
     [not found] <fa.huj8e2v.10ggghn@ifi.uio.no>
     [not found] ` <fa.o5cc8mv.12h4to1@ifi.uio.no>
2002-05-27 12:10   ` Andreas Hartmann
2002-05-27 11:52     ` Zwane Mwaikambo
  -- strict thread matches above, loose matches on Subject: below --
2002-05-27  9:40 Andreas Hartmann
2002-05-27 10:28 ` Florian Weimer
2002-05-27 12:02 ` Alan Cox

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=20020528184643.A796@localhost \
    --to=vdb@mail.ru \
    --cc=linux-kernel@vger.kernel.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