linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: Ryan Wang <openspace.wang@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	kernelnewbies@nl.linux.org
Subject: Re: oom killer and long-waiting processes
Date: Thu, 10 Jun 2010 23:56:30 +0700	[thread overview]
Message-ID: <AANLkTinXqriwgslQwjmjYaGjiyVK4oh1HZcTwxgWCZkh@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik6xP9vVEyW4QG-4RfZu-iEuHcl2pBV_-mfHP4y@mail.gmail.com>

Hi

On Thu, Jun 10, 2010 at 14:17, Ryan Wang <openspace.wang@gmail.com> wrote:
> Hi all,
>
>        I have one question about oom killer:
> If many processes dealing with network communications,
> but due to bad network traffic, the processes have to wait
> for a very long time. And meanwhile they may consume
> some memeory separately for computation. The number
> of such processes may be large.


Please refer to my article here :
http://linuxdevcenter.com/pub/a/linux/2006/11/30/linux-out-of-memory.html

Right now, I can not recall entirely about the rules, but IIRC the
processes that do I/O get lower "score". But that doesn't mean it
won't be killed if free memory amount is really low...

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-06-10 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10  7:17 Ryan Wang
2010-06-10 16:56 ` Mulyadi Santosa [this message]
2010-06-10 20:32 ` David Rientjes
2010-06-11  0:34   ` Ryan Wang

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=AANLkTinXqriwgslQwjmjYaGjiyVK4oh1HZcTwxgWCZkh@mail.gmail.com \
    --to=mulyadi.santosa@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=openspace.wang@gmail.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