From: Sha Zhengju <handai.szj@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: cgroups@vger.kernel.org, mhocko@suse.cz,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Sha Zhengju <handai.szj@taobao.com>
Subject: Re: [PATCH V5] memcg, oom: provide more precise dump info while memcg oom happening
Date: Fri, 21 Dec 2012 11:40:52 +0800 [thread overview]
Message-ID: <CAFj3OHXBFg=xZbvFwWwMQNipC0mCn2hS9pFH59HDmzS9YKqz4Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1212191439530.32757@chino.kir.corp.google.com>
> I'd ask that you put a limit on the number of memcgs you print statistics
> for to prevent spamming the kernel log, otherwise it would be trivial to
> overwrite the entire buffer. Do we really need the memory statistics forank
> the memcg 32 levels above us, for example?
Yeah, now there is no limit on numbers of printed memcg. But do we really
need to build so complicate memcg hierarchy for 32 levels? There is no
such usage now at least in our environment. : )
Thanks,
Sha
--
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>
prev parent reply other threads:[~2012-12-21 3:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 13:51 Sha Zhengju
2012-12-19 15:07 ` Michal Hocko
2012-12-19 22:12 ` Andrew Morton
2012-12-20 13:15 ` Michal Hocko
2012-12-21 3:55 ` Sha Zhengju
2012-12-19 22:42 ` David Rientjes
2012-12-21 3:40 ` Sha Zhengju [this message]
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='CAFj3OHXBFg=xZbvFwWwMQNipC0mCn2hS9pFH59HDmzS9YKqz4Q@mail.gmail.com' \
--to=handai.szj@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=handai.szj@taobao.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--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