linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: David Rientjes <rientjes@google.com>,
	Zhouping Liu <zliu@redhat.com>,
	linux-mm@kvack.org, Li Zefan <lizefan@huawei.com>,
	CAI Qian <caiqian@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	aneesh.kumar@linux.vnet.ibm.com
Subject: Re: memcg: cat: memory.memsw.* : Operation not supported
Date: Thu, 28 Jun 2012 11:29:34 -0700	[thread overview]
Message-ID: <20120628182934.GD22641@google.com> (raw)
In-Reply-To: <20120628123611.GA16042@tiehlicka.suse.cz>

Hello, Michal.

On Thu, Jun 28, 2012 at 02:36:11PM +0200, Michal Hocko wrote:
> @@ -2726,6 +2726,9 @@ static int cgroup_addrm_files(struct cgroup *cgrp, struct cgroup_subsys *subsys,
>  	int err, ret = 0;
>  
>  	for (cft = cfts; cft->name[0] != '\0'; cft++) {
> +		if (subsys->cftype_enabled && !subsys->cftype_enabled(cft->name))
> +			continue;
> +
>  		if (is_add)
>  			err = cgroup_add_file(cgrp, subsys, cft);
>  		else

I hope we could avoid this dynamic decision.  That was one of the main
reasons behind doing the cftype thing.  It's better to be able to
"declare" these kind of things rather than being able to implement
fully flexible dynamic logic.  Too much flexibility often doesn't
achieve much while being a hindrance to evolution of code base (trying
to improve / simplify X - ooh... there's this single wacko corner case
YYY here which is really different from all other users).

really_do_swap_account can't change once booted, right?  Why not just
separate out memsw cfts into a separate array and call
cgroup_add_cftypes() from init path?  Can't we do that from
enable_swap_cgroup()?

Thanks.

-- 
tejun

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-06-28 18:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2a1a74bf-fbb5-4a6e-b958-44fff8debff2@zmail13.collab.prod.int.phx2.redhat.com>
2012-06-27  3:49 ` memcg: cat: memory.memsw.* : Operation not supported Zhouping Liu
2012-06-27 15:48   ` Michal Hocko
2012-06-27 20:04     ` David Rientjes
2012-06-27 20:09       ` Tejun Heo
2012-06-27 20:21         ` David Rientjes
2012-06-27 20:24           ` Tejun Heo
2012-06-27 20:26             ` David Rientjes
2012-06-28  4:04             ` Kamezawa Hiroyuki
2012-06-28 18:31               ` Tejun Heo
2012-06-30  3:45                 ` Kamezawa Hiroyuki
2013-01-21  8:39                   ` Zhouping Liu
2013-01-21 10:56                     ` Michal Hocko
2013-01-21 11:12                       ` Michal Hocko
2013-01-21 13:27                       ` Zhouping Liu
2013-01-21 13:46                         ` Michal Hocko
2012-06-29  7:16               ` Glauber Costa
2012-06-28 12:36       ` Michal Hocko
2012-06-28 18:29         ` Tejun Heo [this message]
2012-06-29  0:11           ` Kamezawa Hiroyuki

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=20120628182934.GD22641@google.com \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=caiqian@redhat.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizefan@huawei.com \
    --cc=mhocko@suse.cz \
    --cc=rientjes@google.com \
    --cc=zliu@redhat.com \
    /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).