From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andreas Hartmann <andihartmann@freenet.de>, linux-kernel@vger.kernel.org
Subject: Re: Memory management in Kernel 2.4.x
Date: Mon, 27 May 2002 16:37:18 +0200 [thread overview]
Message-ID: <3CF2449E.9000905@loewe-komp.de> (raw)
In-Reply-To: <fa.iklie8v.5k2hbj@ifi.uio.no> <fa.na0lviv.e2a93a@ifi.uio.no> <actahk$6bp$1@ID-44327.news.dfncis.de> <3CF23893.207@loewe-komp.de> <1022513156.1126.289.camel@irongate.swansea.linux.org.uk>
Alan Cox wrote:
> On Mon, 2002-05-27 at 14:45, Peter Wächtler wrote:
>
>>There is still the oom killer (Out Of Memory).
>>But it doesn't trigger and the machine pages "forever".
>>Usually kswapd eats the CPU then, discarding and reloading pages,
>>searching lists for pages to evict and so on.
>>
>
> On a -ac kernel with mode 2 or 3 set for overcommit you have to run out
> of kernel resources to hang the box. It won't go OOM because it can't.
> That wouldn't be a VM bug but a leak or poor handling of kernel
> allocations somewhere. Sadly the changes needed to do that (beancounter
> patch) were things Linus never accepted for 2.4
>
I heard of the "beancounter patch" several times now.
Where is it - that beancounter patch? What does it besides bean counting ;-)
ah, googled it:
ftp://ftp.sw.com.sg/pub/Linux/people/saw/kernel/user_beancounter/UserBeancounter.html
I think we will get another candidate for beancounting: the futexes are locking
user pages.. and I already thought about accounting with
setrlimit/ulimit and "max locked memory (kbytes)"
next prev parent reply other threads:[~2002-05-27 14:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.iklie8v.5k2hbj@ifi.uio.no>
[not found] ` <fa.na0lviv.e2a93a@ifi.uio.no>
2002-05-27 12:58 ` Memory management in Kernel 2.4.x 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 [this message]
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
2002-05-28 14:46 Dmitry Volkoff
[not found] <fa.n12rl6v.9644rg@ifi.uio.no>
[not found] ` <fa.jd9c9pv.190gl8n@ifi.uio.no>
2002-05-28 5:42 ` Andreas Hartmann
2002-05-28 11:49 ` Alan Cox
2002-05-28 18:14 ` Andreas Hartmann
[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=3CF2449E.9000905@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andihartmann@freenet.de \
--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