On Fri 18-09-15 18:01:59, Tejun Heo wrote:
> Hello,
>
> Once cgroup/for-4.4 gets propagated to mm, this should apply cleanly.
> Alternatively, I can apply it through the cgroup tree. Which would
> you prefer?
I am OK to go via your tree as well.
--
Michal Hocko
SUSE Labs
--
To unsubscribe from
On Fri, Sep 18, 2015 at 06:01:59PM -0400, Tejun Heo wrote:
> cgroup core only recently grew generic notification support. Wire up
> "memory.events" so that it triggers a file modified event whenever its
> content changes.
>
> v2: Refreshed on top of mem_cgroup relocation.
>
> Signed-off-by:
On Fri, Sep 18, 2015 at 06:01:59PM -0400, Tejun Heo wrote:
> cgroup core only recently grew generic notification support. Wire up
> "memory.events" so that it triggers a file modified event whenever its
> content changes.
>
> v2: Refreshed on top of mem_cgroup relocation.
>
> Signed-off-by:
On Fri 18-09-15 18:01:59, Tejun Heo wrote:
> Hello,
>
> Once cgroup/for-4.4 gets propagated to mm, this should apply cleanly.
> Alternatively, I can apply it through the cgroup tree. Which would
> you prefer?
I am OK to go via your tree as well.
--
Michal Hocko
SUSE Labs
--
To unsubscribe from
cgroup core only recently grew generic notification support. Wire up
"memory.events" so that it triggers a file modified event whenever its
content changes.
v2: Refreshed on top of mem_cgroup relocation.
Signed-off-by: Tejun Heo
Acked-by: Michal Hocko
Cc: Li Zefan
Cc: Johannes Weiner
---
cgroup core only recently grew generic notification support. Wire up
"memory.events" so that it triggers a file modified event whenever its
content changes.
v2: Refreshed on top of mem_cgroup relocation.
Signed-off-by: Tejun Heo
Acked-by: Michal Hocko
Cc:
6 matches
Mail list logo