From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm@kvack.org
Subject: Re: [patch] mm, oom: replace some information in tasklist dump
Date: Mon, 25 Jun 2012 03:37:21 -0400 [thread overview]
Message-ID: <4FE81531.90500@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206241340400.13297@chino.kir.corp.google.com>
(6/24/12 4:43 PM), David Rientjes wrote:
> On Fri, 22 Jun 2012, KOSAKI Motohiro wrote:
>
>>>> No worth to make fragile ABI. Do you have any benefit?
>>>>
>>>
>>> Yes, because this is exactly where we would discover something like a
>>> mm->nr_ptes accounting issue since it would result in an oom kill and we'd
>>> notice the mismatch between nr_ptes and rss in the tasklist dump.
>>
>> Below patch is better, then. tasklist dump should show brief summary and
>> final killed process output should show most detail info. And, now all of
>> get_mm_rss() callsite got consistent.
>>
>
> No, it's not.
>
> Your patch is factoring ptes into get_mm_rss() throughout the kernel, my
> patch is showing get_mm_rss() and nr_ptes in the oom killer tasklist dump
> since they are both (currently) factored in seperately. They are two
> functionally different changes.
I said they should not showed separetly. That's all. Don't request talk the
same repeat.
> If you want to factor ptes into get_mm_rss() and make that change
> throughout the kernel, then you should patch linux-next which includes my
> oom patch, write an actual changelog for why ptes should now be included
> in get_mm_rss() -- which I'll nack because it significantly changes
> /proc/pid/stat output for applications between kernel versions that we
> depend very heavily on -- and propose it seperately.
--
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:[~2012-06-25 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 21:45 [patch] mm, oom: replace some information in tasklist dump David Rientjes
2012-06-22 22:54 ` KOSAKI Motohiro
2012-06-22 23:10 ` David Rientjes
2012-06-22 23:12 ` KOSAKI Motohiro
2012-06-22 23:36 ` David Rientjes
2012-06-23 0:19 ` KOSAKI Motohiro
2012-06-24 20:43 ` David Rientjes
2012-06-25 7:37 ` KOSAKI Motohiro [this message]
2012-06-25 9:16 ` David Rientjes
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=4FE81531.90500@gmail.com \
--to=kosaki.motohiro@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--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).