From: "Om Narasimhan" <om.turyx@gmail.com>
To: linux-mm@kvack.org
Subject: Re: [RFC] [PATCH] support for oom_die
Date: Tue, 11 Apr 2006 10:39:08 -0700 [thread overview]
Message-ID: <6b4e42d10604111039y7c2920bdr2e33cce3873da9ed@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0604111025110.564@schroedinger.engr.sgi.com>
> A user process can cause an oops by using too much memory? Would it not be
> better to terminate the rogue process instead? Otherwise any user can
> bring down the system?
How can we differentiate a rogue process requestion huge amount of
memory and a legitimate process requesting huge amount of memory? Or
do you mean despite the status, kill the process that request huge
amounts of memory?
Om.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-04-11 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 5:29 KAMEZAWA Hiroyuki
2006-04-11 17:28 ` Christoph Lameter
2006-04-11 17:39 ` Om Narasimhan [this message]
2006-04-12 0:37 ` David Chinner
2006-04-12 1:11 ` KAMEZAWA Hiroyuki
2006-04-12 3:31 ` Rik van Riel
2006-04-12 4:49 ` KAMEZAWA Hiroyuki
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=6b4e42d10604111039y7c2920bdr2e33cce3873da9ed@mail.gmail.com \
--to=om.turyx@gmail.com \
--cc=linux-mm@kvack.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