[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimytfrDnr_5SzBUFQu0SaGdAWDC0p38hiFiHrtU@mail.gmail.com>
Date: Mon, 24 Jan 2011 00:38:06 -0800
From: Paul Menage <menage@...gle.com>
To: Ben Blum <bblum@...rew.cmu.edu>
Cc: linux-kernel@...r.kernel.org,
containers@...ts.linux-foundation.org, akpm@...ux-foundation.org,
ebiederm@...ssion.com, lizf@...fujitsu.com, matthltc@...ibm.com,
oleg@...hat.com, David Rientjes <rientjes@...gle.com>,
Miao Xie <miaox@...fujitsu.com>
Subject: Re: [PATCH v7 2/3] cgroups: add atomic-context per-thread subsystem callbacks
Hi Ben,
Finally finding a moment to actually look at these patches. Sorry it's
been a while. Can you send the patches inline rather than as
attachments in future?
Reviewed-by: Paul Menage <menage@...gle.com>
This patch looks fine, although I think that freezer_can_attach_task()
could be simplified to:
static int freezer_can_attach_task(struct cgroup *cgrp, struct task_struct *tsk)
{
if (__cgroup_freezing_or_frozen(tsk))
return -EBUSY;
return 0;
}
since we guarantee that rcu_read_lock() is held across this call.
There appears to be a tiny bit of rot in kernel/cpu.c (due to the
addition of the exit() callback) and memcontrol.c (due to some changes
at the start of mem_cgroup_move_task()) but neither impact actual
code.
I think that before actually pushing to mainline, we'll need to sort
out the cpuset mempolicy yielding issue, since that could be a
user-visible API change.
Paul
View attachment "cgroup-subsys-task-callbacks.patch" of type "text/plain" (22352 bytes)
Powered by blists - more mailing lists