From: Michal Hocko <mhocko@suse.cz>
To: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Cc: Arend van Spriel <arend@broadcom.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
"David S. Miller" <davem@davemloft.net>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
Balbir Singh <bsingharora@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ying Han <yinghan@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"Nikunj A. Dadhania" <nikunj@linux.vnet.ibm.com>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Ciju Rajan K <ciju@linux.vnet.ibm.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: [PATCH V2 1/1][cleanup] memcg: renaming of mem variable to memcg
Date: Wed, 17 Aug 2011 14:43:40 +0200 [thread overview]
Message-ID: <20110817124339.GA10245@tiehlicka.suse.cz> (raw)
In-Reply-To: <20110812070623.28939.4733.sendpatchset@oc5400248562.ibm.com>
Sorry for late reply
On Fri 12-08-11 12:36:23, Raghavendra K T wrote:
> The memcg code sometimes uses "struct mem_cgroup *mem" and sometimes uses
> "struct mem_cgroup *memcg". This patch renames all mem variables to memcg in
> source file.
>
> Testing : Compile tested with following configurations.
> 1) make defconfig ARCH=i386 + CONFIG_CGROUP_MEM_RES_CTLR=y
> CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y CONFIG_CGROUP_MEM_RES_CTLR_SWAP_ENABLED=y
>
> Binary size Before patch
> ========================
> text data bss dec hex filename
> 8911169 520464 1884160 11315793 acaa51 vmlinux
>
> Binary Size After patch
> =======================
> text data bss dec hex filename
> 8911169 520464 1884160 11315793 acaa51 vmlinux
It would be much nicer to see unchanged md5sum. I am not sure how much
possible is this with current gcc or whether special command line
parameters have to be used (at least !CONFIG_DEBUG_INFO* is necessary)
but simple variable rename shouldn't be binary visible.
I guess that a similar approach was used during 32b and 64b x86
unification.
>
> 2) make defconfig ARCH=i386 + CONFIG_CGROUP_MEM_RES_CTLR=y
> CONFIG_CGROUP_MEM_RES_CTLR_SWAP=n CONFIG_CGROUP_MEM_RES_CTLR_SWAP_ENABLED=n
I would assume the same testing results as above
>
> 3) make defconfig ARCH=i386 CONFIG_CGROUP_MEM_RES_CTLR=n
> CONFIG_CGROUP_MEM_RES_CTLR_SWAP=n CONFIG_CGROUP_MEM_RES_CTLR_SWAP_ENABLED=n
ditto.
>
> Other sanity check:
> Bootable configuration on x86 (T60p) with CONFIG_CGROUP_MEM_RES_CTLR=y
> CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y CONFIG_CGROUP_MEM_RES_CTLR_SWAP_ENABLED=y
> is tesed with basic mounting of memcgroup, creation of child and parallel fault.
> mkdir -p /cgroup
> mount -t cgroup none /cgroup -o memory
> mkdir /cgroup/0
> echo $$ > /cgroup/0/tasks
> time ./parallel_fault 2 100000 32
>
> real 0m0.025s
> user 0m0.001s
> sys 0m0.033s
This looks like a random test. I wouldn't add it to the changelog.
--
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9
Czech Republic
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-17 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 7:06 [PATCH V2 1/1][cleanup] memcg: renaming of mem variable to memcg Raghavendra K T
2011-08-17 12:43 ` Michal Hocko [this message]
2011-08-19 6:21 ` Raghavendra K T
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=20110817124339.GA10245@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=arend@broadcom.com \
--cc=bsingharora@gmail.com \
--cc=ciju@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linville@tuxdriver.com \
--cc=mchehab@redhat.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=vatsa@linux.vnet.ibm.com \
--cc=yinghan@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).