From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: Sergey Dyasly <dserrg@gmail.com>
Cc: cgroups@vger.kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Michal Hocko <mhocko@suse.cz>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH][trivial] memcg: Kconfig info update
Date: Mon, 27 May 2013 12:24:38 -0400 [thread overview]
Message-ID: <CAHGf_=pyEP=zJ80HSKAojymSmW=S1s+1QFN663OXD8RtonLVmA@mail.gmail.com> (raw)
In-Reply-To: <1369668984-2787-1-git-send-email-dserrg@gmail.com>
On Mon, May 27, 2013 at 11:36 AM, Sergey Dyasly <dserrg@gmail.com> wrote:
> Now there are only 2 members in struct page_cgroup.
> Update config MEMCG description accordingly.
>
> Signed-off-by: Sergey Dyasly <dserrg@gmail.com>
> ---
> init/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index 9d3a788..16d1502 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -876,7 +876,7 @@ config MEMCG
>
> Note that setting this option increases fixed memory overhead
> associated with each page of memory in the system. By this,
> - 20(40)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
> + 8(16)bytes/PAGE_SIZE on 32(64)bit system will be occupied by memory
> usage tracking struct at boot. Total amount of this is printed out
> at boot.
Yes, kernel developers often foget to update documentations. Nice catch!
Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
--
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:[~2013-05-27 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 15:36 Sergey Dyasly
2013-05-27 15:46 ` Michal Hocko
2013-05-27 16:24 ` KOSAKI Motohiro [this message]
2013-05-28 14:53 ` Johannes Weiner
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='CAHGf_=pyEP=zJ80HSKAojymSmW=S1s+1QFN663OXD8RtonLVmA@mail.gmail.com' \
--to=kosaki.motohiro@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=dserrg@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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