From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
paul-inf54ven1CmVyaH7bEyXVA@public.gmane.org,
glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
mhocko-AlSwsSmVLrQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCHSET] cpuset: drop cpuset->stack_list and ->parent, take#2
Date: Thu, 3 Jan 2013 13:44:03 -0800 [thread overview]
Message-ID: <1357249446-25075-1-git-send-email-tj@kernel.org> (raw)
Hello, guys.
This is the second take of "drop cpuset->stack_list and ->parent"
patchset. Other than being rebased on top of v3.8-rc2 + "cpuset:
decouple cpuset locking from cgroup core, take#2", nothing really has
changed.
The original patchset description follows.
cpuset implements its own descendant iteration using
cpuset->stack_list and has its own ->parent pointer. There's nothing
cpuset specific about descendant walking or finding the parent. This
patchset makes cpuset use cgroup generic API instead.
0001-cpuset-implement-cgroup_rightmost_descendant.patch
0002-cpuset-replace-cpuset-stack_list-with-cpuset_for_eac.patch
0003-cpuset-remove-cpuset-parent.patch
0001 implements cgroup_rightmost_descendant() which can be used to
skip subtree during pre-order tree walk. Michal, maybe memcg can use
it too?
0002 replaces cpuset->stack_list with generic
for_each_descendasnt_pre().
0003 replaces cpuset->parent with cgroup->parent.
This patchset is on top of
v3.8-rc2 d1c3ed669a2d452cacfb48c2d171a1f364dae2ed
+ [1] "[PATCHSET cgroup/for-3.8] cpuset: decouple cpuset locking from cgroup core, take#2"
and available in the following git branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-cpuset-iter
include/linux/cgroup.h | 1
kernel/cgroup.c | 26 ++++++++
kernel/cpuset.c | 151 +++++++++++++++++++++----------------------------
3 files changed, 92 insertions(+), 86 deletions(-)
Thanks.
--
tejun
[1] http://thread.gmane.org/gmane.linux.kernel.cgroups/5629
next reply other threads:[~2013-01-03 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 21:44 Tejun Heo [this message]
[not found] ` <1357249446-25075-1-git-send-email-tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2013-01-03 21:44 ` [PATCH 1/3] cpuset: implement cgroup_rightmost_descendant() Tejun Heo
2013-01-03 21:44 ` [PATCH 2/3] cpuset: replace cpuset->stack_list with cpuset_for_each_descendant_pre() Tejun Heo
2013-01-03 21:44 ` [PATCH 3/3] cpuset: remove cpuset->parent Tejun Heo
2013-01-06 9:27 ` [PATCHSET] cpuset: drop cpuset->stack_list and ->parent, take#2 Li Zefan
[not found] ` <50E94392.2050509-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-01-07 16:47 ` Tejun Heo
[not found] ` <20130107164707.GI3926-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-01-07 16:52 ` Tejun Heo
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=1357249446-25075-1-git-send-email-tj@kernel.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
--cc=paul-inf54ven1CmVyaH7bEyXVA@public.gmane.org \
--cc=peterz-wEGCiKHe2LqWVfeAwA7xHQ@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 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).