From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Subject: RE: System hang problem.
Date: Wed, 4 Oct 2006 17:24:12 +0300 [thread overview]
Message-ID: <200610041724.12514.a1426z@gawab.com> (raw)
Manish Neema wrote:
> > What you can often do, if you have one application using much memory,
> > is limiting *this application's* memory usage with ulimit. If the
> > application correctly handles malloc()==NULL, then at least your
> > system will behave stably.
>
> The problem is its different application, different user each time (a
> typical large R&D environment). /etc/security/limits.conf allows to set
> max resident set size. Is there a way to limit based on the total
> virtual size?
You mean like: ulimit -v [total VMsize/runqueue]
I suppose, that this could easily be dynamically calculated by the kernel,
for a tremendously inhibiting OOM-killer effect.
Thanks!
--
Al
next reply other threads:[~2006-10-04 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 14:24 Al Boldi [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 5:44 Manish Neema
2006-10-04 0:07 Manish Neema
2006-10-04 0:49 ` Alan Cox
2006-10-04 3:26 ` Willy Tarreau
2006-10-04 9:53 ` Jarek Poplawski
2006-10-03 22:07 Manish Neema
2006-10-03 23:35 ` Keith Mannthey
2006-10-04 0:33 ` 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=200610041724.12514.a1426z@gawab.com \
--to=a1426z@gawab.com \
--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
Powered by JetHome