From: Minchan Kim <minchan.kim@gmail.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 5/5] add NR_ANON_PAGES to OOM log
Date: Mon, 6 Jul 2009 00:27:20 +0900 [thread overview]
Message-ID: <28c262360907050827y577c3859g5e05e82935e96010@mail.gmail.com> (raw)
In-Reply-To: <20090705151628.GA11307@localhost>
On Mon, Jul 6, 2009 at 12:16 AM, Wu Fengguang<fengguang.wu@intel.com> wrote:
> On Sun, Jul 05, 2009 at 11:04:17PM +0800, Minchan Kim wrote:
>> On Sun, Jul 5, 2009 at 10:19 PM, KOSAKI
>> Motohiro<kosaki.motohiro@jp.fujitsu.com> wrote:
>> >>> > > + printk("%ld total anon pages\n", global_page_state(NR_ANON_PAGES));
>> >>> > > printk("%ld total pagecache pages\n", global_page_state(NR_FILE_PAGES));
>> >>> >
>> >>> > Can we put related items together, ie. this looks more friendly:
>> >>> >
>> >>> > Anon:XXX active_anon:XXX inactive_anon:XXX
>> >>> > File:XXX active_file:XXX inactive_file:XXX
>> >>>
>> >>> hmmm. Actually NR_ACTIVE_ANON + NR_INACTIVE_ANON != NR_ANON_PAGES.
>> >>> tmpfs pages are accounted as FILE, but it is stay in anon lru.
>> >>
>> >> Right, that's exactly the reason I propose to put them together: to
>> >> make the number of tmpfs pages obvious.
>> >>
>> >>> I think your proposed format easily makes confusion. this format cause to
>> >>> imazine Anon = active_anon + inactive_anon.
>> >>
>> >> Yes it may confuse normal users :(
>> >>
>> >>> At least, we need to use another name, I think.
>> >>
>> >> Hmm I find it hard to work out a good name.
>> >>
>> >> But instead, it may be a good idea to explicitly compute the tmpfs
>> >> pages, because the excessive use of tmpfs pages could be a common
>> >> reason of OOM.
>> >
>> > Yeah, explicite tmpfs/shmem accounting is also useful for /proc/meminfo.
>>
>> Do we have to account it explicitly?
>
> When OOM happens, one frequent question to ask is: are there too many
> tmpfs/shmem pages? Exporting this number makes our oom-message-decoding
> life easier :)
Indeed.
>> If we know the exact isolate pages of each lru,
>>
>> tmpfs/shmem = (NR_ACTIVE_ANON + NR_INACTIVE_ANON + isolate(anon)) -
>> NR_ANON_PAGES.
>>
>> Is there any cases above equation is wrong ?
>
> That's right, but the calculation may be too complex (and boring) for
> our little brain ;)
Yes. if something is change in future or we miss someting, the above
question may be wrong.
I wanted to remove overhead of new accouting.
Anyway, I think it's not a big cost in normal system.
So If you want to add new accounting, I don't have any objection. :)
> Thanks,
> Fengguang
>
--
Kind regards,
Minchan Kim
--
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>
next prev parent reply other threads:[~2009-07-05 17:43 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 9:22 [PATCH 0/5] OOM analysis helper patches KOSAKI Motohiro
2009-07-05 9:23 ` [PATCH 1/5] add per-zone statistics to show_free_areas() KOSAKI Motohiro
2009-07-05 11:05 ` Wu Fengguang
2009-07-05 11:09 ` KOSAKI Motohiro
2009-07-05 11:14 ` Wu Fengguang
2009-07-07 16:33 ` Christoph Lameter
2009-07-05 9:24 ` [PATCH 2/5] add buffer cache information " KOSAKI Motohiro
2009-07-05 11:21 ` Wu Fengguang
2009-07-05 11:31 ` KOSAKI Motohiro
2009-07-05 12:07 ` Wu Fengguang
2009-07-05 14:16 ` Minchan Kim
2009-07-06 4:24 ` KOSAKI Motohiro
2009-07-05 9:24 ` [PATCH 3/5] Show kernel stack usage to /proc/meminfo and OOM log KOSAKI Motohiro
2009-07-07 16:37 ` Christoph Lameter
2009-07-09 2:13 ` KOSAKI Motohiro
2009-07-09 21:00 ` Christoph Lameter
2009-07-05 9:25 ` [PATCH 4/5] add isolate pages vmstat KOSAKI Motohiro
2009-07-05 12:10 ` Wu Fengguang
2009-07-05 12:23 ` KOSAKI Motohiro
2009-07-05 14:51 ` Minchan Kim
2009-07-06 9:28 ` KOSAKI Motohiro
2009-07-06 11:55 ` KOSAKI Motohiro
2009-07-07 0:01 ` Minchan Kim
2009-07-07 0:07 ` KOSAKI Motohiro
2009-07-07 1:19 ` KOSAKI Motohiro
2009-07-07 1:48 ` Minchan Kim
2009-07-07 2:12 ` KOSAKI Motohiro
2009-07-07 2:31 ` Minchan Kim
2009-07-07 3:02 ` Rik van Riel
2009-07-07 13:51 ` Wu Fengguang
2009-07-07 16:49 ` Christoph Lameter
2009-07-07 17:23 ` Rik van Riel
2009-07-07 23:32 ` Christoph Lameter
2009-07-09 2:19 ` KOSAKI Motohiro
2009-07-09 21:00 ` Christoph Lameter
2009-07-07 16:46 ` Christoph Lameter
2009-07-08 1:44 ` Wu Fengguang
2009-07-05 9:26 ` [PATCH 5/5] add NR_ANON_PAGES to OOM log KOSAKI Motohiro
2009-07-05 12:13 ` Wu Fengguang
2009-07-05 12:21 ` KOSAKI Motohiro
2009-07-05 13:02 ` Wu Fengguang
2009-07-05 13:19 ` KOSAKI Motohiro
2009-07-05 15:04 ` Minchan Kim
2009-07-05 15:16 ` Wu Fengguang
2009-07-05 15:27 ` Minchan Kim [this message]
2009-07-07 16:53 ` Christoph Lameter
2009-07-09 5:50 ` KOSAKI Motohiro
2009-07-09 7:20 ` KOSAKI Motohiro
2009-07-09 10:27 ` Minchan Kim
2009-07-07 1:22 ` KOSAKI Motohiro
2009-07-07 10:54 ` Wu Fengguang
2009-07-07 13:56 ` Wu Fengguang
2009-07-09 5:13 ` KOSAKI Motohiro
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=28c262360907050827y577c3859g5e05e82935e96010@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).