From: Johannes Weiner <hannes@cmpxchg.org>
To: Tejun Heo <tj@kernel.org>
Cc: lizefan@huawei.com, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, mhocko@suse.cz, vgoyal@redhat.com,
axboe@kernel.dk
Subject: Re: [PATCHSET cgroup/for-3.17] cgroup, blkcg, memcg: make blkcg depend on memcg on unified hierarchy
Date: Mon, 7 Jul 2014 14:33:29 -0400 [thread overview]
Message-ID: <20140707183329.GC1149@cmpxchg.org> (raw)
In-Reply-To: <1403917392-32555-1-git-send-email-tj@kernel.org>
On Fri, Jun 27, 2014 at 09:03:06PM -0400, Tejun Heo wrote:
> Hello, guys.
>
> Currently, the blkio subsystem attributes all of writeback IOs to the
> root. One of the issues is that there's no way to tell who originated
> a writeback IO from block layer. Those IOs are usually issued
> asynchronously from a task which didn't have anything to do with
> actually generating the dirty pages. The memory subsystem, when
> enabled, already keeps track of the ownership of each dirty page and
> it's desirable for blkio to piggyback instead of adding its own
> per-page tag.
>
> This can be achieved on the unified hierarchy without too much
> difficulty. This patchset implements a dependency mechanism in the
> cgroup such that a subsystem can depends on other subsystems. If
> available, the depended-upon subsystems are enabled together
> implicitly when the subsystem is turned on. Implicitly enabled
> subsystems are invisible and the dependencies are transparent to
> userland.
>
> This patchset implements the dependency mechanism in cgroup core and
> make blkcg depend on memcg. This doesn't actually solve the writeback
> problem yet but is an important step.
>
> This patchset contains the following six patches.
>
> 0001-cgroup-reorganize-cgroup_subtree_control_write.patch
> 0002-cgroup-introduce-cgroup-subtree_control.patch
> 0003-cgroup-make-interface-files-visible-iff-enabled-on-c.patch
> 0004-cgroup-implement-cgroup_subsys-css_reset.patch
> 0005-cgroup-implement-cgroup_subsys-depends_on.patch
> 0006-blkcg-memcg-make-blkcg-depend-on-memcg-on-the-defaul.patch
These look good to me.
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
We can update memcg's ->css_reset() as we re-populate the interface in
the default hierarchy.
next prev parent reply other threads:[~2014-07-07 18:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 1:03 Tejun Heo
2014-06-28 1:03 ` [PATCH 1/6] cgroup: reorganize cgroup_subtree_control_write() Tejun Heo
2014-06-28 1:03 ` [PATCH 2/6] cgroup: introduce cgroup->subtree_control Tejun Heo
2014-06-28 1:03 ` [PATCH 3/6] cgroup: make interface files visible iff enabled on cgroup->subtree_control Tejun Heo
2014-06-28 1:03 ` [PATCH 4/6] cgroup: implement cgroup_subsys->css_reset() Tejun Heo
2014-06-28 1:03 ` [PATCH 5/6] cgroup: implement cgroup_subsys->depends_on Tejun Heo
2014-06-28 1:03 ` [PATCH 6/6] blkcg, memcg: make blkcg depend on memcg on the default hierarchy Tejun Heo
2014-06-28 11:49 ` [PATCH v2 " Tejun Heo
2014-07-08 19:42 ` Vivek Goyal
2014-07-08 21:53 ` Tejun Heo
2014-07-09 11:57 ` Vivek Goyal
2014-07-04 6:29 ` [PATCHSET cgroup/for-3.17] cgroup, blkcg, memcg: make blkcg depend on memcg on unified hierarchy Li Zefan
2014-07-07 18:33 ` Johannes Weiner [this message]
2014-07-08 22:03 ` 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=20140707183329.GC1149@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mhocko@suse.cz \
--cc=tj@kernel.org \
--cc=vgoyal@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
Powered by JetHome