From: Glauber Costa <glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
To: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>
Subject: Re: [PATCH 0/2] page_cgroup cleanups
Date: Fri, 5 Apr 2013 15:32:27 +0400 [thread overview]
Message-ID: <515EB64B.8010104@parallels.com> (raw)
In-Reply-To: <1365156072-24100-1-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
On 04/05/2013 02:01 PM, Glauber Costa wrote:
> Hi,
>
> Last time I sent the mem cgroup bypass patches, Kame and Michal pointed out
> that some of it was a bit of cleanup, specifically at the page_cgroup side.
> I've decided to separate those patches and send them separately. After these
> patches are applied, page_cgroup will be initialized together with the root
> cgroup, instead of init/main.c
>
> When we move cgroup initialization to the first non-root cgroup created, all
> we'll have to do from the page_cgroup side would be to move the initialization
> that now happens at root, to the first child.
>
> Glauber Costa (2):
> memcg: consistently use vmalloc for page_cgroup allocations
> memcg: defer page_cgroup initialization
>
> include/linux/page_cgroup.h | 21 +------------------
> init/main.c | 2 --
> mm/memcontrol.c | 2 ++
> mm/page_cgroup.c | 51 +++++++++++++++------------------------------
> 4 files changed, 20 insertions(+), 56 deletions(-)
>
FYI: There are kbuild warnings with this. I wanted to send it earlier to
see what people think. If there is no changes requested, please let me
know I will send a new version with just the kbuild fixes folded.
WARNING: multiple messages have this Message-ID (diff)
From: Glauber Costa <glommer@parallels.com>
To: cgroups@vger.kernel.org
Cc: linux-mm@kvack.org, kamezawa.hiroyu@jp.fujitsu.com,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>
Subject: Re: [PATCH 0/2] page_cgroup cleanups
Date: Fri, 5 Apr 2013 15:32:27 +0400 [thread overview]
Message-ID: <515EB64B.8010104@parallels.com> (raw)
In-Reply-To: <1365156072-24100-1-git-send-email-glommer@parallels.com>
On 04/05/2013 02:01 PM, Glauber Costa wrote:
> Hi,
>
> Last time I sent the mem cgroup bypass patches, Kame and Michal pointed out
> that some of it was a bit of cleanup, specifically at the page_cgroup side.
> I've decided to separate those patches and send them separately. After these
> patches are applied, page_cgroup will be initialized together with the root
> cgroup, instead of init/main.c
>
> When we move cgroup initialization to the first non-root cgroup created, all
> we'll have to do from the page_cgroup side would be to move the initialization
> that now happens at root, to the first child.
>
> Glauber Costa (2):
> memcg: consistently use vmalloc for page_cgroup allocations
> memcg: defer page_cgroup initialization
>
> include/linux/page_cgroup.h | 21 +------------------
> init/main.c | 2 --
> mm/memcontrol.c | 2 ++
> mm/page_cgroup.c | 51 +++++++++++++++------------------------------
> 4 files changed, 20 insertions(+), 56 deletions(-)
>
FYI: There are kbuild warnings with this. I wanted to send it earlier to
see what people think. If there is no changes requested, please let me
know I will send a new version with just the kbuild fixes folded.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-04-05 11:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 10:01 [PATCH 0/2] page_cgroup cleanups Glauber Costa
2013-04-05 10:01 ` Glauber Costa
[not found] ` <1365156072-24100-1-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-04-05 10:01 ` [PATCH 1/2] memcg: consistently use vmalloc for page_cgroup allocations Glauber Costa
2013-04-05 10:01 ` Glauber Costa
[not found] ` <1365156072-24100-2-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-04-05 12:06 ` Johannes Weiner
2013-04-05 12:06 ` Johannes Weiner
[not found] ` <20130405120604.GN1953-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2013-04-05 12:27 ` Glauber Costa
2013-04-05 12:27 ` Glauber Costa
[not found] ` <515EC34C.8040704-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-04-05 16:25 ` Johannes Weiner
2013-04-05 16:25 ` Johannes Weiner
[not found] ` <20130405162536.GO1953-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2013-04-09 2:41 ` Kamezawa Hiroyuki
2013-04-09 2:41 ` Kamezawa Hiroyuki
2013-04-05 10:01 ` [PATCH 2/2] memcg: defer page_cgroup initialization Glauber Costa
2013-04-05 10:01 ` Glauber Costa
2013-04-05 11:32 ` Glauber Costa [this message]
2013-04-05 11:32 ` [PATCH 0/2] page_cgroup cleanups Glauber Costa
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=515EB64B.8010104@parallels.com \
--to=glommer-bzqdu9zft3wakbo8gow8eq@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@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.