From: Justin A <justin@bouncybouncy.net>
To: "Dr. Kelsey Hudson" <kernel@blackhole.compendium-tech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VM nuisance
Date: Thu, 16 Aug 2001 20:24:12 -0400 [thread overview]
Message-ID: <20010816202412.B20072@bouncybouncy.net> (raw)
In-Reply-To: <20010816192946.A20072@bouncybouncy.net> <Pine.LNX.4.33.0108161704250.10866-100000@sol.compendium-tech.com>
In-Reply-To: <Pine.LNX.4.33.0108161704250.10866-100000@sol.compendium-tech.com>
Wouldn't it be just a matter of
case 'f': /* F -- oom handlder _f_ree memory */
printk("Run OOM Handler\n");
oom_kill();
break;
in handle_sysrq in sysrq.c?
-Justin
On Thu, Aug 16, 2001 at 05:06:40PM -0700, Dr. Kelsey Hudson wrote:
> On Thu, 16 Aug 2001, Justin A wrote:
>
> > Though it is not a complete solution for all cases(servers etc),
> > could a SysReq combination be added that triggers OOM? I'm sure many
> > people use SysReq-k on occasion to get a system out of endless
> > swapping, I think having a SysReq key for OOM would be a great
> > improvement.
> >
> > Comments?
>
> I think it's a damn good idea. I'd actually begin coding that now, if I
> knew where to start. SysRQ has saved my life more than once -- i'm sure it
> would help all the other people who are having problems with randomized
> thrashing and stuff.
>
> Kelsey Hudson khudson@ctica.com
> Software Engineer
> Compendium Technologies, Inc (619) 725-0771
> ---------------------------------------------------------------------------
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-08-17 0:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9li6sf$h5$1@ns1.clouddancer.com>
2001-08-11 1:30 ` David Ford
2001-08-11 2:48 ` Rik van Riel
2001-08-11 2:59 ` H. Peter Anvin
2001-08-11 4:17 ` Rik van Riel
2001-08-11 4:40 ` David Ford
2001-08-11 4:46 ` Rik van Riel
2001-08-11 4:41 ` safemode
2001-08-11 5:00 ` H. Peter Anvin
2001-08-11 13:13 ` Alan Cox
2001-08-11 15:39 ` David Ford
2001-08-11 3:50 ` safemode
2001-08-12 13:09 ` Maciej Zenczykowski
2001-08-12 13:45 ` Rik van Riel
2001-08-16 23:29 ` Justin A
2001-08-17 0:06 ` Dr. Kelsey Hudson
2001-08-17 0:24 ` Justin A [this message]
2001-08-17 2:54 ` Dr. Kelsey Hudson
2001-08-12 23:05 ` Dan Mann
2001-08-13 0:01 ` Colonel
2001-08-13 14:32 ` dean gaudet
2001-08-13 19:47 ` Brian
2001-08-14 8:27 ` Helge Hafting
2001-08-17 13:34 ` Szabolcs Szakacsits
2001-08-17 17:29 ` Rik van Riel
2001-08-14 14:00 ` "VM watchdog"? [was Re: VM nuisance] Pavel Machek
2001-08-16 22:24 ` Jakob Østergaard
2001-08-17 1:26 ` David Ford
2001-08-17 1:41 ` Jakob Østergaard
2001-08-17 9:04 ` Colonel
2001-08-17 20:38 ` David Ford
[not found] <20010811035112.59EC438D01@perninha.conectiva.com.br>
2001-08-11 3:52 ` VM nuisance Rik van Riel
[not found] <no.id>
2001-08-11 16:45 ` 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=20010816202412.B20072@bouncybouncy.net \
--to=justin@bouncybouncy.net \
--cc=kernel@blackhole.compendium-tech.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
all inboxes | Powered by JetHome®