From: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>
To: Sergey Dyasly <dserrg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
KAMEZAWA Hiroyuki
<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Subject: Re: [PATCH][trivial] memcg: Kconfig info update
Date: Mon, 27 May 2013 17:46:38 +0200 [thread overview]
Message-ID: <20130527154638.GK27274@dhcp22.suse.cz> (raw)
In-Reply-To: <1369668984-2787-1-git-send-email-dserrg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
CCing Andrew
On Mon 27-05-13 19:36:24, Sergey Dyasly wrote:
> Now there are only 2 members in struct page_cgroup.
> Update config MEMCG description accordingly.
>
> Signed-off-by: Sergey Dyasly <dserrg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Acked-by: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>
> ---
> 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.
>
> --
> 1.8.1.2
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2013-05-27 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 15:36 [PATCH][trivial] memcg: Kconfig info update Sergey Dyasly
[not found] ` <1369668984-2787-1-git-send-email-dserrg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-27 15:46 ` Michal Hocko [this message]
2013-05-27 16:24 ` KOSAKI Motohiro
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=20130527154638.GK27274@dhcp22.suse.cz \
--to=mhocko-alswssmvlrq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dserrg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.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