From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-team-b10kYP2dOMg@public.gmane.org
Subject: [PATCHSET] cgroup: reorganize cgroup source files
Date: Tue, 20 Dec 2016 16:08:19 -0500 [thread overview]
Message-ID: <20161220210827.11176-1-tj@kernel.org> (raw)
cgroup source files are getting a bit too unwieldy. Let's reorganize
them.
* Move cgroup files in kernel to kernel/cgroup.
* Split cgroup.c into multiple files.
The only functional change this patchset causes is loss of a
WARN_ON(); otherwise, everything remains identical.
This patchset contains the following eight patches.
0001-cgroup-reorder-css_set-fields.patch
0002-cgroup-move-cgroup-files-under-kernel-cgroup.patch
0003-cgroup-move-cgroup-v1-specific-code-to-kernel-cgroup.patch
0004-cgroup-refactor-mount-path-and-clearly-distinguish-v.patch
0005-cgroup-separate-out-cgroup1_kf_syscall_ops.patch
0006-cgroup-move-v1-mount-functions-to-kernel-cgroup-cgro.patch
0007-cgroup-rename-functions-for-consistency.patch
0008-cgroup-move-namespace-code-to-kernel-cgroup-namespac.patch
The patchset is available in the following git branch
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-cgroup-reorg
and on top of the following git branch
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-cgroup2-procs
diffstat follows. Thanks.
include/linux/cgroup-defs.h | 54 -
kernel/Makefile | 5
kernel/cgroup/Makefile | 5
kernel/cgroup/cgroup-internal.h | 155 +++
kernel/cgroup/cgroup-v1.c | 1395 ++++++++++++++++++++++++++++
kernel/cgroup/cgroup.c | 1940 +++-------------------------------------
kernel/cgroup/namespace.c | 155 +++
7 files changed, 1907 insertions(+), 1802 deletions(-)
--
tejun
next reply other threads:[~2016-12-20 21:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 21:08 Tejun Heo [this message]
2016-12-20 21:08 ` [PATCH 1/8] cgroup: reorder css_set fields Tejun Heo
2016-12-20 21:08 ` [PATCH 3/8] cgroup: move cgroup v1 specific code to kernel/cgroup/cgroup-v1.c Tejun Heo
[not found] ` <20161220210827.11176-4-tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-12-20 22:00 ` [PATCH v2 " Tejun Heo
2016-12-20 21:08 ` [PATCH 4/8] cgroup: refactor mount path and clearly distinguish v1 and v2 paths Tejun Heo
2016-12-20 21:08 ` [PATCH 5/8] cgroup: separate out cgroup1_kf_syscall_ops Tejun Heo
2016-12-20 21:08 ` [PATCH 7/8] cgroup: rename functions for consistency Tejun Heo
[not found] ` <20161220210827.11176-1-tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-12-20 21:08 ` [PATCH 2/8] cgroup: move cgroup files under kernel/cgroup/ Tejun Heo
2016-12-20 21:08 ` [PATCH 6/8] cgroup: move v1 mount functions to kernel/cgroup/cgroup-v1.c Tejun Heo
2016-12-20 21:08 ` [PATCH 8/8] cgroup: move namespace code to kernel/cgroup/namespace.c Tejun Heo
2016-12-22 17:29 ` [PATCH 9/8] cgroup: fix RCU related sparse warnings Tejun Heo
2016-12-26 6:23 ` [PATCHSET] cgroup: reorganize cgroup source files Zefan Li
2016-12-27 19:53 ` 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=20161220210827.11176-1-tj@kernel.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=kernel-team-b10kYP2dOMg@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@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).