mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samium Gromoff <_deepfire@mail.ru>
To: andrea@suse.de
Cc: linux-kernel@vger.kernel.org, riel@surriel.com
Subject: OOM /proc logging
Date: Fri, 2 Nov 2001 12:02:06 +0300 (MSK)	[thread overview]
Message-ID: <200111020902.fA292A818161@vegae.deep.net> (raw)

        Hello folks...
     After another complain on #kernelnewbies about the OOM killer doing
  strange thingss, by killing small processes when its really not needed,
  and not doing anything when its really OOM i ran out of nerves and came out
  with an idea, which i believe already settled down is some brains.
    I speak about providing in /proc list of process badnesses, possibly with
  some additional info...
    Its just a shame to have a stable kernel randomly killing processes even when 
  its not needed...

  (this message was planned as answer to Linus request for any kind of VM bitchig....)

regards, Samium Gromoff

             reply	other threads:[~2001-11-02  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02  9:02 Samium Gromoff [this message]
2001-11-02 14:31 ` Andrea Arcangeli
     [not found] <no.id>
2001-11-02  9:06 ` Samium Gromoff

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=200111020902.fA292A818161@vegae.deep.net \
    --to=_deepfire@mail.ru \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@surriel.com \
    /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®