public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "BALBIR SINGH" <balbir.singh@wipro.com>
To: linux-kernel@vger.kernel.org
Subject: [RFC] OOM aware applications
Date: Tue, 25 Sep 2001 10:49:15 +0530	[thread overview]
Message-ID: <3BB013D3.6060408@wipro.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

I was looking at the code in oom_kill.c, I had the following suggestions

Warning: I am not aware of what was discussed earlier about these issues 
or if they were discusses at all.

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.

2. Minor changes suggested

    In the code, I see

    points *= 2 and points /= 4 in a few places, recommend changing them to

    points <<= 1 and points >>= 2 to help the compiler generate better code


Dialog between the kernel and an OOM aware application

on OOM condition

kernel to the application: Hey u  are running the system out of memory
application: Sorry my lord, I commited a blunder and will rectify myself

application rectifies itself and everybody lives happily everafter
application is stuborn

kernel: You must go now, u have been unfair in your demands and have 
caused a lot of problem
application: Does not get to say anything, it is zapped

Comments, Suggestions, Criticism
Balbir




[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 853 bytes --]

----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------


             reply	other threads:[~2001-09-25  5:18 UTC|newest]

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

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=3BB013D3.6060408@wipro.com \
    --to=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