Re: Mem issues in 2.6.9 (ever since 2.6.9-rc3) and possible cause

From: Nick Piggin (nickpiggin_at_yahoo.com.au)
Date: 10/26/04

  • Next message: Adrian Bunk: "Re: My thoughts on the "new development model"" 
    Date:	Tue, 26 Oct 2004 18:01:46 +1000
To: Andrew Morton <akpm@osdl.org>

    Andrew Morton wrote:
    > Rik van Riel <riel@redhat.com> wrote:
    >
    >>- if (referenced && page_mapping_inuse(page))
    >>+ if (referenced && sc->priority && page_mapping_inuse(page))
    >
    >
    > Makes heaps of sense, but I'd like to exactly understand why people are
    > getting oomings before doing something like this. I think we're still
    > waiting for a testcase?

    I have found that quite often it is because all_unreclaimable gets set,
    scanning slows down, and the OOM killer goes off.

    Rik, I wonder if you can put some printk's where all_unreclaimable
    is being set to 1, and see if there is any correlation to OOMs?

    Aside from that, the patch does make sense, but might be too aggressive.
    In heavy swapping loads, the "zero priority" scan might make up a
    significant proportion of the scanning done so you'll want to be
    careful about regressions there.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Adrian Bunk: "Re: My thoughts on the "new development model""

    Relevant Pages

    • Re: OK to set PF_MEMDIE on cleanup tasks?
      ... > from killing the task again. ... The PF_MEMDIE flag is there so the oom killer doesn't just sit there ... The SIGTERM behaviour is there because the CAP_SYS_RAWIO process may need ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] oom_pardon, aka dont kill my xlock
      ... that worried (I know user non-overcommit is not a perfect solution). ... I was picking at the OOM Killer rather than at you - you just ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: VM Problems in 2.6.7 (Too active OOM Killer)
      ... > the above the oom killer will still get screwed by mlock and it simply ... > -ENOMEM with syscalls if you fill the whole lowmem zone. ... isn't getting much traction is because it's too broad to correlate to ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] oom killer (Core)
      ... > behavioral changes in the OOM killer, ... > several instances of bad OOM killer behavior already, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)