linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Andrew Morton <akpm@digeo.com>
Cc: riel@redhat.com, nikita@clusterfs.com, linux-mm@kvack.org,
	piggin@cyberone.com.au
Subject: Re: [PATCH] ignore referenced pages on reclaim when OOM
Date: Wed, 10 Nov 2004 18:09:22 -0200	[thread overview]
Message-ID: <20041110200922.GE12867@logos.cnet> (raw)
In-Reply-To: <20041110142900.09552f7f.akpm@digeo.com>

On Wed, Nov 10, 2004 at 02:29:00PM -0800, Andrew Morton wrote:
> Marcelo Tosatti <marcelo.tosatti@cyclades.com> wrote:
> >
> > So z->all_unreclaimable logic and "OOM detection" are conflicting goals.
> 
> Only in a single case: where a zone is all_unreclaimable and some pages
> have recently become reclaimable but we don't know about it yet.

The thing is - if you dont scan the zones "enough" you have no way of 
reliably knowing it is OOM.

But on the other hand, scanning it wastes CPU time - what you call "mad scanning".

They are two extremes, I feel we need a balance between them.

> Certainly it can happen, but it sounds really unlikely to me.  So I suspect
> that if you were to fix that problem by some means, it wouldn't help
> anything.
> 
>But maybe I'm wrong, or maybe the all_unreclaimable logic has rotted. 

I dont think all_unreclaimable logic is rotted - it does what what it is
expected to do. 

At least thats how I see things, maybe I'm wrong and it is indeed rotted.

> Have you tried simply disabling it?

Tried now - if I disable it then balance_pgdat() detects the OOM situation by noticing
its not successful freeing pages (thus setting worked_dma and worked_normal, 
see patch), and kills the memory hog. Side note, the memory hog runs _much_ faster
without all_unreclaimable logic.

I'll continue hacking on this tomorrow.

As always, thanks for the input :D

--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-11-10 20:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 18:18 Marcelo Tosatti
2004-11-08 21:48 ` Nikita Danilov
2004-11-08 21:56   ` Rik van Riel
2004-11-08 18:48     ` Marcelo Tosatti
2004-11-08 22:28     ` Andrew Morton
2004-11-10 18:41       ` Marcelo Tosatti
2004-11-10 22:29         ` Andrew Morton
2004-11-10 20:09           ` Marcelo Tosatti [this message]
2004-11-12 16:10           ` Rik van Riel

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=20041110200922.GE12867@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=akpm@digeo.com \
    --cc=linux-mm@kvack.org \
    --cc=nikita@clusterfs.com \
    --cc=piggin@cyberone.com.au \
    --cc=riel@redhat.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