All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Jesper Juhl <jj-IYz4IdjRLj0sV2N9l4h3zg@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
	Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	Pavel Emelianov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] cgroup: prefer [kv]zalloc over [kv]malloc+memset in memory controller code.
Date: Tue, 2 Nov 2010 10:37:53 +0530	[thread overview]
Message-ID: <20101102050752.GG3769__14022.3135510043$1288674629$gmane$org@balbir.in.ibm.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1011012038490.12889-h2p7t3/P30RzeRGmFJ5qR7ZzlVVXadcDXqFh9Ls21Oc@public.gmane.org>

* Jesper Juhl <jj-IYz4IdjRLj0sV2N9l4h3zg@public.gmane.org> [2010-11-01 20:40:56]:

> Hi (please CC me on replies),
> 
> 
> Apologies to those who receive this multiple times. I screwed up the To: 
> field in my original mail :-(
> 
> 
> In mem_cgroup_alloc() we currently do either kmalloc() or vmalloc() then 
> followed by memset() to zero the memory. This can be more efficiently 
> achieved by using kzalloc() and vzalloc().
> 
> 
> Signed-off-by: Jesper Juhl <jj-IYz4IdjRLj0sV2N9l4h3zg@public.gmane.org>
> ---
>  memcontrol.c |    5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 9a99cfa..90da698 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -4199,14 +4199,13 @@ static struct mem_cgroup *mem_cgroup_alloc(void)
> 
>  	/* Can be very big if MAX_NUMNODES is very big */
>  	if (size < PAGE_SIZE)
> -		mem = kmalloc(size, GFP_KERNEL);
> +		mem = kzalloc(size, GFP_KERNEL);
>  	else
> -		mem = vmalloc(size);
> +		mem = vzalloc(size);
> 
>  	if (!mem)
>  		return NULL;
> 
> -	memset(mem, 0, size);
>  	mem->stat = alloc_percpu(struct mem_cgroup_stat_cpu);
>  	if (!mem->stat) {
>  		if (size < PAGE_SIZE)
>

 
Acked-by: Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
 

-- 
	Three Cheers,
	Balbir

  parent reply	other threads:[~2010-11-02  5:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 19:40 [PATCH] cgroup: prefer [kv]zalloc over [kv]malloc+memset in memory controller code Jesper Juhl
2010-11-01 19:40 ` Jesper Juhl
2010-11-01 19:58 ` Hiroyuki Kamezawa
2010-11-01 19:58   ` Hiroyuki Kamezawa
2010-11-01 20:01 ` Johannes Weiner
2010-11-01 20:01   ` Johannes Weiner
2010-11-01 19:59   ` Jesper Juhl
2010-11-01 19:59     ` Jesper Juhl
2010-11-01 23:21     ` Minchan Kim
2010-11-01 23:21       ` Minchan Kim
     [not found]     ` <alpine.LNX.2.00.1011012056250.12889-h2p7t3/P30RzeRGmFJ5qR7ZzlVVXadcDXqFh9Ls21Oc@public.gmane.org>
2010-11-01 23:21       ` Minchan Kim
2010-11-02 12:24       ` Johannes Weiner
2010-11-03 14:15       ` Wu Fengguang
2010-11-02 12:24     ` Johannes Weiner
2010-11-02 12:24       ` Johannes Weiner
2010-11-03 14:15     ` Wu Fengguang
2010-11-03 14:15       ` Wu Fengguang
     [not found]   ` <20101101200122.GH840-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2010-11-01 19:59     ` Jesper Juhl
2010-11-02  5:07 ` Balbir Singh
2010-11-02  5:07   ` Balbir Singh
     [not found] ` <alpine.LNX.2.00.1011012038490.12889-h2p7t3/P30RzeRGmFJ5qR7ZzlVVXadcDXqFh9Ls21Oc@public.gmane.org>
2010-11-01 19:58   ` Hiroyuki Kamezawa
2010-11-01 20:01   ` Johannes Weiner
2010-11-02  5:07   ` Balbir Singh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-01 19:40 Jesper Juhl
2010-11-01 19:35 Jesper Juhl
2010-11-01 23:11 ` Minchan Kim
     [not found] ` <alpine.LNX.2.00.1011012030150.12889-h2p7t3/P30RzeRGmFJ5qR7ZzlVVXadcDXqFh9Ls21Oc@public.gmane.org>
2010-11-01 23:11   ` Minchan Kim
2010-11-01 19:35 Jesper Juhl

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='20101102050752.GG3769__14022.3135510043$1288674629$gmane$org@balbir.in.ibm.com' \
    --to=balbir-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=jj-IYz4IdjRLj0sV2N9l4h3zg@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
    --cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=xemul-GEFAQzZX7r8dnm+yROfE0A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.