From: Olaf Hering <olh@suse.de>
To: Michel Lanners <mlan@cpu.lu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Out of memory?
Date: Mon, 12 Jun 2000 13:42:56 +0200 [thread overview]
Message-ID: <20000612134256.B12226@suse.de> (raw)
In-Reply-To: <200006121039.MAA03014@piglet.grunz.lu>
On Mon, Jun 12, Michel Lanners wrote:
> Jun 12 10:53:13 piglet kernel: VM: killing process gimp
> Jun 12 10:55:03 piglet kernel: VM: killing process X
> Jun 12 10:59:46 piglet kernel: VM: killing process X
> Jun 12 12:04:27 piglet kernel: VM: killing process xfs
>
> and so on... acording to the comment in arch/ppc/mm/fault.c, this
> happens when for some reason the kernel cannot satisfy a paging request.
>
> xfs gets killed when rendering a really big font, X when sending it over
> to gimp, and gimp when working with large images....
>
> What reason is there to kill a process for memory reasons? Does a single
> process need to fit _entirely_ into RAM, or can part of a process be
> swapped out? In all of the above cases, I've always had over 100 megs of
> swap free. Or is there a fixed limit on how big a process can get?
It is only self protection of the kernel to run not out of memory.
The last process that want to allocate memory when memory is low gets
killed. Looks like that is not smart enough when swap is still
available.
Gruss Olaf
--
$ man clone
BUGS
Main feature not yet implemented...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-12 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-12 10:39 Out of memory? Michel Lanners
2000-06-12 11:42 ` Olaf Hering [this message]
2000-06-12 12:46 ` Michael Schmitz
-- strict thread matches above, loose matches on Subject: below --
2002-01-30 14:58 Out of memory ? GOTZON ASTONDOA
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=20000612134256.B12226@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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;
as well as URLs for NNTP newsgroup(s).