netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Daniel Borkmann <dborkman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: <pablo-Cap9r6Oaw4JrovVCs/uTlw@public.gmane.org>,
	<netfilter-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	<cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH nf-next v3] netfilter: xtables: lightweight process control group matching
Date: Sat, 28 Dec 2013 17:54:20 +0800	[thread overview]
Message-ID: <52BE9FCC.6020708@huawei.com> (raw)
In-Reply-To: <52BE97DC.5090807-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>

>> Thinking about this further a bit, with this separation into net/core/, you
>> would need another Kconfig, where people choose between built-in or
>> module (or none).
> 
> Just disable module support for net_cgroup_classid. I never like the cgroup
> feature that allows modular subsystems. It will be just about 100 lines of
> code, so we gain little by making it modular. Futhermore with this change,
> we can simplify include/linux/cls_cgroup.h
> 
> Moreoever cls_cgroup is the only modular cgroup subsystem, so I may even remove
> this feature from cgroup core after the change to cls_cgroup.
> 
>> With built-in you would disallow people to load/unload the
>> cgroup part during runtime. With the module, you would introduce a module
>> dependency _for each_, even if you only want to use net_cls, which sort of
>> is not what we want from a simple "cleanup".
>>

Even if it's a module, I don't think there's any dependency here, as
the only interface that cls_cgroup and netfilter_cgroup need is
task_cls_classid(), which is an inline function and doesn't involve any
EXPORT symbol.

Therefore it works even if CONFIG_CLS_CGROUP doesn't depend of
CONFIG_NET_CGROUP_CLASSID.

  parent reply	other threads:[~2013-12-28  9:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1387815795.git.dborkman@redhat.com>
     [not found] ` <cover.1387815795.git.dborkman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-12-23 17:41   ` [PATCH nf-next v3] netfilter: xtables: lightweight process control group matching Daniel Borkmann
2013-12-27  3:13     ` Li Zefan
     [not found]       ` <52BCF04B.3070908-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-12-27  8:05         ` Daniel Borkmann
     [not found]           ` <52BD34D1.1040708-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-12-28  1:33             ` Li Zefan
2013-12-28  8:17               ` Daniel Borkmann
     [not found]                 ` <52BE8936.6000001-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-12-28  8:44                   ` Daniel Borkmann
     [not found]                     ` <52BE8F50.4080005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-12-28  9:20                       ` Li Zefan
     [not found]                         ` <52BE97DC.5090807-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-12-28  9:54                           ` Li Zefan [this message]
2013-12-28 18:04                           ` Daniel Borkmann
2013-12-28 18:37                             ` Daniel Borkmann

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=52BE9FCC.6020708@huawei.com \
    --to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=dborkman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=netfilter-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pablo-Cap9r6Oaw4JrovVCs/uTlw@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@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).