From: Andi Kleen <andi@firstfloor.org>
To: Andrea <andrea256it@yahoo.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: super root shell/mode/api
Date: Sun, 17 May 2009 17:02:40 +0200 [thread overview]
Message-ID: <87iqjzpyb3.fsf@basil.nowhere.org> (raw)
In-Reply-To: <861928.62033.qm@web23602.mail.ird.yahoo.com> (Andrea's message of "Sun, 17 May 2009 13:06:53 +0000 (GMT)")
Andrea <andrea256it@yahoo.it> writes:
>
> I know there is an OOM handling, but the only thing that
> happened was the hard disk light flashing for more or less 30 minutes
> and I was forced to press the reset button and my data was lost :(
One trick I found very useful to make OOM much less painful is to
make the swap partition small (not zero though).
The traditional suggestion of 2x RAM is far too large on modern
systems and since Linux is rather inefficient at swapping having
so much swap space just prolongs the death struggle.
With a smaller swap partition (not more than 100-200MB) the OOM killer kicks in
relatively quickly when something goes wrong and kills the offending process.
> I think it would be simply awesome to have a Linux Kernel mode
> similar to the c-64 cartridge concept.
>
> Maybe call it in honor to the c-64 'cartridge freeze mode' or so :)
>
> You hit a button combination and you enter in a Linux Kernel ncurses menu
> and/or shell and/or GUI, where you can for example:
You could do all that today by using a suitable kexec/kdump kernel setup with
sysrq-C.
The kdump kernel can do all that based on the image of the previous kernel.
Some of it is very easy (e.g. for disassemble just run "crash"), other
parts don't make sense (e.g. swap out processes -- the parent kernel
already did that)
Traditional distributions just dump the image, but there's no
principle reason it couldn't do more.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-05-17 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 13:06 super root shell/mode/api Andrea
2009-05-17 15:02 ` Andi Kleen [this message]
2009-05-18 9:35 ` Alan Cox
2009-05-18 16:12 ` Henrique de Moraes Holschuh
2009-05-20 4:36 ` Willy Tarreau
2009-05-20 6:03 ` Sitsofe Wheeler
-- strict thread matches above, loose matches on Subject: below --
2009-05-17 17:13 Andrea
[not found] <cCSbU-L3-17@gated-at.bofh.it>
2009-05-18 22:56 ` Bodo Eggert
2009-05-19 14:36 Andrea
2009-05-19 14:54 ` Alan Cox
2009-05-23 13:23 ` Bodo Eggert
2009-05-23 13:50 ` Joao Correia
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=87iqjzpyb3.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=andrea256it@yahoo.it \
--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