From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: pomac@vapor.com, Linux-kernel@vger.kernel.org
Subject: Re: [BUG?] OOM with large cache....(x86_64, 2.6.24-rc3-git1, nohz)
Date: Tue, 20 Nov 2007 18:26:34 +1100 [thread overview]
Message-ID: <200711201826.35014.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20071120054648.GA20436@elte.hu>
On Tuesday 20 November 2007 16:46, Ingo Molnar wrote:
> * Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> > Unfortunately, we don't show NR_ANON_PAGES in these stats, [...]
>
> sidenote: the way i combat these missing pieces of instrumentation in
> the scheduler is to add them immediately to the cfs-debug-info.sh script
> (and to /proc/sched_debug if needed). I.e. if we get one report that
> misses a piece of critical information is OK, but if it's two reports
> and we still havent made it easy to report the right kind of information
> that is our fault entirely. This constant ping-ponging for information
> that goes on for basically every MM problem - which information could
> have been provided in the first message (by running a single, easy to
> download tool) is getting pretty hindering i believe.
I do usually to add the stats as I've needed them. I haven't
specifically needed NR_ANON_PAGES for an oom-killer problem
before, but I've added plenty of other output there.
(it's in /proc/meminfo of course, which is the most useful...)
next prev parent reply other threads:[~2007-11-20 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 0:59 [BUG?] OOM with large cache....(x86_64, 2.6.24-rc3-git1, nohz) Ian Kumlien
2007-11-20 4:13 ` Nick Piggin
2007-11-20 5:46 ` Ingo Molnar
2007-11-20 7:26 ` Nick Piggin [this message]
2007-11-20 8:59 ` Nick Piggin
2007-11-20 9:09 ` Ian Kumlien
2007-11-20 10:47 ` Nick Piggin
2007-11-20 12:05 ` iank
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=200711201826.35014.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pomac@vapor.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.