From: Neil Horman <nhorman@tuxdriver.com>
To: Jianyu Zhan <nasa4836@gmail.com>
Cc: davem@davemloft.net, lizefan@huawei.com, tj@kernel.org,
daniel.wagner@bmw-carit.de, gaofeng@cn.fujitsu.com,
stephen@networkplumber.org, jiri@resnulli.us,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netprio_cgroup: explicitly init the early_init field
Date: Tue, 22 Apr 2014 07:19:06 -0400 [thread overview]
Message-ID: <20140422111906.GD17116@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1398144722-9864-1-git-send-email-nasa4836@gmail.com>
On Tue, Apr 22, 2014 at 01:32:02PM +0800, 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.
>
> Signed-off-by: Jianyu Zhan <nasa4836@gmail.com>
> ---
> net/core/netprio_cgroup.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/net/core/netprio_cgroup.c b/net/core/netprio_cgroup.c
> index 13ddd68..fc21035 100644
> --- a/net/core/netprio_cgroup.c
> +++ b/net/core/netprio_cgroup.c
> @@ -250,6 +250,7 @@ struct cgroup_subsys net_prio_cgrp_subsys = {
> .css_free = cgrp_css_free,
> .attach = net_prio_attach,
> .base_cftypes = ss_files,
> + .early_init = 0,
> };
>
> static int netprio_device_event(struct notifier_block *unused,
> --
> 2.0.0-rc0
>
>
NACK, for the same reason that it doesn't make sense for net_classid.
Early_init should already be zero. What problem are you trying to solve here?
Neil
next prev parent reply other threads:[~2014-04-22 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 5:32 Jianyu Zhan
2014-04-22 11:19 ` Neil Horman [this message]
2014-04-22 11:25 ` Jianyu Zhan
2014-04-22 16:13 ` David Miller
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=20140422111906.GD17116@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=daniel.wagner@bmw-carit.de \
--cc=davem@davemloft.net \
--cc=gaofeng@cn.fujitsu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=nasa4836@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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
all inboxes | Powered by JetHome®