From: Li Zefan <lizefan@huawei.com>
To: Jianyu Zhan <nasa4836@gmail.com>
Cc: <davem@davemloft.net>, <tj@kernel.org>, <nhorman@tuxdriver.com>,
<aris@redhat.com>, <dborkman@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] netclassid_cgroup: explicitly init the early_init field
Date: Tue, 22 Apr 2014 14:28:34 +0800 [thread overview]
Message-ID: <53560C12.2050309@huawei.com> (raw)
In-Reply-To: <1398144676-9739-1-git-send-email-nasa4836@gmail.com>
On 2014/4/22 13:31, Jianyu Zhan wrote:
> For a cgroup subsystem who should init early, then it should carefully
> take care of the implementation of css_alloc, because it will be called
> before mm_init() setup the world.
>
> Luckily we don't, and we better explicitly assign the early_init field
> to 0, for document reason.
>
The initialization is redundant, and your reason is not reasonable.
> Signed-off-by: Jianyu Zhan <nasa4836@gmail.com>
nack
> ---
> net/core/netclassid_cgroup.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/net/core/netclassid_cgroup.c b/net/core/netclassid_cgroup.c
> index 22931e1..1b07dca 100644
> --- a/net/core/netclassid_cgroup.c
> +++ b/net/core/netclassid_cgroup.c
> @@ -108,4 +108,5 @@ struct cgroup_subsys net_cls_cgrp_subsys = {
> .css_free = cgrp_css_free,
> .attach = cgrp_attach,
> .base_cftypes = ss_files,
> + .early_init = 0,
> };
>
next prev parent reply other threads:[~2014-04-22 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 5:31 [PATCH] netclassid_cgroup: explicitly init the early_init field Jianyu Zhan
2014-04-22 6:28 ` Li Zefan [this message]
2014-04-22 11:02 ` Neil Horman
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=53560C12.2050309@huawei.com \
--to=lizefan@huawei.com \
--cc=aris@redhat.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nasa4836@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--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;
as well as URLs for NNTP newsgroup(s).