public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: BALBIR SINGH <balbir.singh@wipro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] OOM aware applications
Date: Tue, 25 Sep 2001 10:46:22 -0600	[thread overview]
Message-ID: <20010925104622.B392@turbolinux.com> (raw)
In-Reply-To: <3BB013D3.6060408@wipro.com>
In-Reply-To: <3BB013D3.6060408@wipro.com>

On Sep 25, 2001  10:49 +0530, BALBIR SINGH wrote:
> Warning: I am not aware of what was discussed earlier about these issues 
> or if they were discusses at all.

They have been discussed many times.  Please search for SIGDANGER in the
linux-kernel mailing list archive.

> 1. I was wondering that instead of killing the application using 
>    oom_kill_task() directly, should the OOM issue some kind of a
>    warning by sending a signal (some signal with si_code set to a
>    value indicating that the application is causing memory to run
>    out). Then, wait for a while and then see if the application is
>    still misbehaving and if so kill it.

This is exactly what SIGDANGER is.

Cheers, Andreas
--
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert


      parent reply	other threads:[~2001-09-25 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25  5:19 [RFC] OOM aware applications BALBIR SINGH
2001-09-25 11:05 ` Matthias Andree
2001-09-25 16:46 ` Andreas Dilger [this message]

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=20010925104622.B392@turbolinux.com \
    --to=adilger@turbolabs.com \
    --cc=balbir.singh@wipro.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