From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Paul Menage <menage@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH -mm 2/2] cgroup: fold struct cg_cgroup_link into struct css_set
Date: Thu, 11 Sep 2008 22:26:50 +0800 [thread overview]
Message-ID: <48C92AAA.6030206@cn.fujitsu.com> (raw)
In-Reply-To: <48C929DF.3050009@cn.fujitsu.com>
sorry for not send to Andrew Morton and send to Paul Menage tiwce.
add [To: Andrew Morton <akpm@linux-foundation.org>]
Thanks, Lai
Lai Jiangshan wrote:
> one struct cg_cgroup_link per link is very waste.
> This way need to allocate struct cg_cgroup_link for
> (css_set_count * hierarchy_count) times. And it will bring fragments
> for memory allocation.
>
next prev parent reply other threads:[~2008-09-11 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 14:23 [RFC PATCH -mm 2/2] cgroup: fold struct cg_cgroup_link into struct css_set Lai Jiangshan
2008-09-11 14:26 ` Lai Jiangshan [this message]
2008-09-11 17:50 ` Paul Menage
2008-09-15 2:01 ` Lai Jiangshan
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=48C92AAA.6030206@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@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