From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: Pavel Machek <pavel@Elf.mj.gts.cz>
Cc: linux-kernel@vger.rutgers.edu, linux-mm <linux-mm@kvack.org>
Subject: Re: Recipe for cooking 2.1.72's mm
Date: Tue, 16 Dec 1997 12:53:36 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.971216124819.15838B-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <19971216091554.50382@Elf.mj.gts.cz>
On Tue, 16 Dec 1997, Pavel Machek wrote:
> Sorry. There is a problem. It needs to be solved, not worked
> around. (Notice, that same process does nothing bad to 2.0.28).
On my system, it just gives one or two out-of-memory kills
of random processes. I'd really like it if those processes
would be a little less random... Killing kerneld or crond
(or X... remember those poor stateless-vga-card users) is
IMHO worse than killing a program from some USER. Finding
the most hoggy non-root process group and killing some of
it's programs shouldn't be too difficult.
btw: I'm using 2.1.66 with my mmap-age patch...
> And: Work around is bad. Imagine your machine with such behaviour on
> 100MBit ethernet. Imagine me around (ping -f)ing your machine. That
> can keep your pages low for as long as I want. You do not your machine
> to go yo-yo (up and down and up and down ...).
Ok, so we should limit the amount of memory the kernel can grab
for internal usage... Sysctl-wise of course, because some people
have special purpose routing machines.
Rik.
+-----------------------------+------------------------------+
| For Linux mm-patches, go to | "I'm busy managing memory.." |
| my homepage (via LinuxHQ). | H.H.vanRiel@fys.ruu.nl |
| ...submissions welcome... | http://www.fys.ruu.nl/~riel/ |
+-----------------------------+------------------------------+
next parent reply other threads:[~1997-12-16 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19971216091554.50382@Elf.mj.gts.cz>
1997-12-16 11:53 ` Rik van Riel [this message]
1997-12-16 13:56 ` Pavel Machek
1997-12-18 4:46 ` zombies Gaurish R Dalvi
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.3.91.971216124819.15838B-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=pavel@Elf.mj.gts.cz \
/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