From: Zefan Li <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>, <hannes@cmpxchg.org>
Cc: <linux-kernel@vger.kernel.org>, <cgroups@vger.kernel.org>,
<kernel-team@fb.com>
Subject: Re: [PATCHSET] cgroup: reorganize cgroup source files
Date: Mon, 26 Dec 2016 14:23:17 +0800 [thread overview]
Message-ID: <5860B755.9000004@huawei.com> (raw)
In-Reply-To: <20161220210827.11176-1-tj@kernel.org>
On 2016/12/21 5:08, Tejun Heo wrote:
> 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(-)
>
Acked-by: Zefan Li <lizefan@huawei.com>
next prev parent reply other threads:[~2016-12-26 6:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 21:08 [PATCHSET] cgroup: reorganize cgroup source files Tejun Heo
2016-12-20 21:08 ` [PATCH 1/8] cgroup: reorder css_set fields Tejun Heo
2016-12-20 21:08 ` [PATCH 2/8] cgroup: move cgroup files under kernel/cgroup/ Tejun Heo
2016-12-20 21:08 ` [PATCH 3/8] cgroup: move cgroup v1 specific code to kernel/cgroup/cgroup-v1.c Tejun Heo
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 6/8] cgroup: move v1 mount functions to kernel/cgroup/cgroup-v1.c Tejun Heo
2016-12-20 21:08 ` [PATCH 7/8] cgroup: rename functions for consistency 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 ` Zefan Li [this message]
2016-12-27 19:53 ` [PATCHSET] cgroup: reorganize cgroup source files 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=5860B755.9000004@huawei.com \
--to=lizefan@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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