The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@interia.pl>
To: linux-kernel@vger.kernel.org
Subject: VM - is "reserved memory for root" possible (in case of a leak)?
Date: Wed, 07 Jul 2004 09:37:42 +0200	[thread overview]
Message-ID: <40EBA846.6010705@interia.pl> (raw)

Hello,

Short nature of a problem:

Recently I was playing with Apache2 as a proxy + mod_clamav as a virus 
scanner, put some load to it, and in a short time hanged the machine 
(actually, it was short of memory, and it stopped to respond - in logs I 
saw VM was killing some other processes, unfortunately not Apache).

As I could reach the machine only remotely, it was no wonder I run into 
troubles...

Sounds familiar?


Solution?

I was thinking, if there is something like:

"reserved_min_memory_for_root = 10M"
"reserved_min_memory_processes = /usr/sbin/sshd, /usr/sbin/pppd, etc.etc"

Which would just give that memory for those processes "once and for 
all", and thus, saving trouble in case of a memory leak, uncontrolled 
process, or similar.

I know it would be tricky to implement it, because the question arises, 
what happens if we have no memory left, and these 
"reserved_min_memory_processes" begin to grow?

But I think it would be something like a comparison:

ulimit vs this "reserved_min_memory_for_root", and
quota vs -m option from mke2fs.

Is there something like it already in the kernel?


It would be similar to mke2fs for the filesystem:

# man mke2fs

-m reserved-blocks-percentage
               Specify the percentage of the filesystem blocks reserved 
for the
               super-user.  This value defaults to 5%



Regards,

Tomasz Chmielewski


             reply	other threads:[~2004-07-07  7:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-07  7:37 Tomasz Chmielewski [this message]
2004-07-07  8:32 ` VM - is "reserved memory for root" possible (in case of a leak)? FabF

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=40EBA846.6010705@interia.pl \
    --to=mangoo@interia.pl \
    --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