All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@novell.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org, Hugh Dickins <hugh@veritas.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: per-process shared information
Date: Fri, 15 Oct 2004 01:58:45 +0200	[thread overview]
Message-ID: <20041014235845.GL17849@dualathlon.random> (raw)
In-Reply-To: <20041014214711.GF6899@logos.cnet>

On Thu, Oct 14, 2004 at 06:47:11PM -0300, Marcelo Tosatti wrote:
> 
> Hi Andrea!
> 
> No useful comments on the statm reporting issue.
> 
> > Ps. if somebody like Hugh volunteers implementing it, you're very
> > welcome, just let me know (I'll eventually want to work on the oom
> > handling too, which is pretty screwed right now, 
> 
> Yes, we've got reports of bad OOM killing behaviour (is that what you're
> talking about?) 
> 
> One thing is the removal of "if (nr_swap_pages > 0) goto out" from oom_kill() 
> causes problems (spurious oom kill). 
> 
> We need to throttle more, on page reclaiming progress I think.
> 
> Take a look at 
> 
> http://marc.theaimsgroup.com/?l=linux-mm&m=109587921204602&w=2
> 
> What else you're seeing?
> 
> > I've plenty of bugs
> > open on that area and the lowmem zone protection needs a rewrite too to
> > be set to a sane default value no matter the pages_lows etc..).
> 
> Nick has been working on that lately I think. What is the problem?

things went worse with the switch from 2.6.8 to 2.6.9-rc, so that's not
the nr_swap_pages > 0, likely the latest changes introduced regressions
instead of fixing them.

I'm seeing both hard deadlocks and suprious oom kills, and that all
makes sense, I can see the bugs, it's just I need to fix them, my plan
is to forward port some code from 2.4 which works fine, objrmap will make
it even better.

  reply	other threads:[~2004-10-15  0:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 23:10 per-process shared information Andrea Arcangeli
2004-10-14 21:47 ` Marcelo Tosatti
2004-10-14 23:58   ` Andrea Arcangeli [this message]
2004-10-14 23:17     ` Marcelo Tosatti
2004-10-15 10:45     ` William Lee Irwin III
2004-10-14 21:49 ` Hugh Dickins
2004-10-14 22:11   ` William Lee Irwin III
2004-10-14 22:37   ` Andrea Arcangeli
2004-10-15 10:51     ` William Lee Irwin III
2004-10-15 11:56     ` Hugh Dickins
2004-10-15 13:19       ` Albert Cahalan
2004-10-15 14:28         ` William Lee Irwin III
2004-10-15 14:40           ` Albert Cahalan
2004-10-15 14:52             ` William Lee Irwin III
2004-10-15 17:02             ` Andrea Arcangeli
2004-10-15 16:20         ` Andrea Arcangeli
2004-10-15 16:31           ` Albert Cahalan
2004-10-15 17:10             ` William Lee Irwin III
2004-10-15 19:29               ` Albert Cahalan
2004-10-15 17:13             ` Andrea Arcangeli
2004-10-15 17:51               ` Albert Cahalan
2004-10-15 18:14                 ` Andrea Arcangeli
2004-10-15 18:30                   ` William Lee Irwin III
2004-10-15 18:40                     ` Andrea Arcangeli
2004-10-15 18:47                       ` William Lee Irwin III
2004-10-15 19:23                         ` Andrea Arcangeli
2004-10-15 20:41                           ` William Lee Irwin III
2004-10-15 20:52                             ` Andrea Arcangeli
2004-10-15 21:16                         ` William Lee Irwin III
2004-10-15 21:28                           ` Andrea Arcangeli
2004-10-15 21:40                             ` William Lee Irwin III
2004-10-15 22:04                               ` Hugh Dickins
2004-10-19 15:09           ` Bill Davidsen
2004-10-15 16:04       ` Andrea Arcangeli
2004-10-19 15:18         ` Bill Davidsen

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=20041014235845.GL17849@dualathlon.random \
    --to=andrea@novell.com \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.