From: Tejun Heo <tj@kernel.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Qiang Huang <h.huangqiang@huawei.com>,
corbet@lwn.net, Zefan Li <lizefan@huawei.com>,
hannes@cmpxchg.org, akpm@linux-foundation.org,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
cgroups@vger.kernel.org
Subject: Re: [PATCH] Documentation/memcg: update kmem limit doc as codes behavior
Date: Thu, 12 May 2016 12:03:22 -0400 [thread overview]
Message-ID: <20160512160322.GU4775@htj.duckdns.org> (raw)
In-Reply-To: <20160511064018.GB16677@dhcp22.suse.cz>
On Wed, May 11, 2016 at 08:40:19AM +0200, Michal Hocko wrote:
> On Wed 11-05-16 14:07:31, Qiang Huang wrote:
> > The restriction of kmem setting is not there anymore because the
> > accounting is enabled by default even in the cgroup v1 - see
> > b313aeee2509 ("mm: memcontrol: enable kmem accounting for all
> > cgroups in the legacy hierarchy").
> >
> > Update docs accordingly.
>
> I am pretty sure there will be other things out of date in that file but
> this is an improvemtn already.
>
> > Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
>
> Acked-by: Michal Hocko <mhocko@suse.com>
Andrew, can you please pick this one up?
Thanks!
--
tejun
--
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:[~2016-05-12 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 8:15 [PATCH] Documentation/memcg: remove restriction of setting kmem limit Qiang Huang
2016-05-05 8:32 ` Michal Hocko
2016-05-11 5:54 ` Qiang Huang
2016-05-11 6:07 ` [PATCH] Documentation/memcg: update kmem limit doc as codes behavior Qiang Huang
2016-05-11 6:40 ` Michal Hocko
2016-05-12 16:03 ` Tejun Heo [this message]
2016-05-14 16:13 ` Jonathan Corbet
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=20160512160322.GU4775@htj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=h.huangqiang@huawei.com \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=mhocko@kernel.org \
/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).