From: Alexey Dobriyan <adobriyan@gmail.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
kamezawa.hiroyu@jp.fujitsu.com,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/7] memcontrol: use simple_malloc()/simple_free()
Date: Sun, 16 Nov 2008 07:54:04 +0300 [thread overview]
Message-ID: <20081116045404.GC24624@x200.localdomain> (raw)
In-Reply-To: <20081116045128.GB24624@x200.localdomain>
On Sun, Nov 16, 2008 at 07:51:28AM +0300, Alexey Dobriyan wrote:
> On Sun, Nov 16, 2008 at 12:33:46PM +0800, Lai Jiangshan wrote:
> > use simple_malloc()/simple_free() instead of current codes.
>
> struct mem_cgroup can't reach the size when kmalloc starts failing.
Or it probably can with big NR_CPUS.
struct mem_cgroup_stat {
struct mem_cgroup_stat_cpu cpustat[NR_CPUS];
};
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -1062,11 +1062,7 @@ static struct mem_cgroup *mem_cgroup_alloc(void)
> > {
> > struct mem_cgroup *mem;
> >
> > - if (sizeof(*mem) < PAGE_SIZE)
> > - mem = kmalloc(sizeof(*mem), GFP_KERNEL);
> > - else
> > - mem = vmalloc(sizeof(*mem));
> > -
> > + mem = simple_malloc(sizeof(*mem));
> > if (mem)
> > memset(mem, 0, sizeof(*mem));
> > return mem;
> > @@ -1074,10 +1070,7 @@ static struct mem_cgroup *mem_cgroup_alloc(void)
> >
> > static void mem_cgroup_free(struct mem_cgroup *mem)
> > {
> > - if (sizeof(*mem) < PAGE_SIZE)
> > - kfree(mem);
> > - else
> > - vfree(mem);
> > + simple_free(mem);
> > }
next prev parent reply other threads:[~2008-11-16 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 4:33 Lai Jiangshan
2008-11-16 4:51 ` Alexey Dobriyan
2008-11-16 4:54 ` Alexey Dobriyan [this message]
2008-11-17 0:09 ` KAMEZAWA Hiroyuki
2008-11-16 5:01 ` Lai Jiangshan
2008-11-16 8:16 ` David Miller
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=20081116045404.GC24624@x200.localdomain \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®