From: Diego Calleja <diegocg@gmail.com>
To: Matthias-Christian Ott <matthias.christian@tiscali.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: make OOM more "user friendly"
Date: Sat, 2 Apr 2005 19:11:40 +0200 [thread overview]
Message-ID: <20050402191140.3de10df2.diegocg@gmail.com> (raw)
In-Reply-To: <424ECF4D.6070800@tiscali.de>
El Sat, 02 Apr 2005 18:58:53 +0200,
Matthias-Christian Ott <matthias.christian@tiscali.de> escribió:
> I disagree this is _not_ usefull. If the user don't knows what OOM means
> he can use google to get this information.
And google will take them to what random source of information? There's no "official"
meaning of what OOM is outside the kernel.... And anyway, why shouldn't the kernel tell
what's happening? That printk is not exactly a fifty-page explanation, it just says "your
system has run out of memory" instead of "OOM", which is what it's really happening and
it's not verbose at all, and it doesn't scare users.
OOM doesn't prints just those messages, if prints a lot of "debugging info" about the state
of the memory subsystem, I've found people in usenet who reboots their systems when
they see that because they think it's a critical failure or something - and looking at how it's
printed, I don't blame them. This is the reason why I submitted this patch.
(and I'd have added a "look at Documentation/oom.txt", but there's zero documentation of
what OOM is, what are the causes of it, tips of how to find apps triggering it and tips to fix
it, and I'm not the right person to write it, so...)
next prev parent reply other threads:[~2005-04-02 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 16:05 Diego Calleja
2005-04-02 16:58 ` Matthias-Christian Ott
2005-04-02 17:11 ` Diego Calleja [this message]
2005-04-02 17:36 ` Indrek Kruusa
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=20050402191140.3de10df2.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.christian@tiscali.de \
/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