From: Frederic Weisbecker <fweisbec@gmail.com>
To: Tejun Heo <tj@kernel.org>, Li Zefan <lizf@cn.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Containers <containers@lists.linux-foundation.org>,
Cgroups <cgroups@vger.kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Paul Menage <paul@paulmenage.org>,
Mandeep Singh Baines <msb@chromium.org>
Subject: [PATCH 0/2 v2] cgroup: Remove useless task_lock()
Date: Wed, 21 Dec 2011 03:02:36 +0100 [thread overview]
Message-ID: <1324432958-20414-1-git-send-email-fweisbec@gmail.com> (raw)
Hi,
It's the same set but rebased on top of cgroup/for-3.3 instead of
Mandeep's patch.
Although the first patch has changed a bit after the rebase
I have kept the Reviewed-by tag of Li and Mandeep because the
core change itself hasn't changed much.
Second patch is the same.
Thanks.
Frederic Weisbecker (2):
cgroup: Remove unnecessary task_lock before fetching css_set on
migration
cgroup: Drop task_lock(parent) on cgroup_fork()
kernel/cgroup.c | 30 +++++++++++++++++-------------
1 files changed, 17 insertions(+), 13 deletions(-)
--
1.7.5.4
next reply other threads:[~2011-12-21 2:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 2:02 Frederic Weisbecker [this message]
2011-12-21 2:02 ` [PATCH 1/2 v2] cgroup: Remove unnecessary task_lock before fetching css_set on migration Frederic Weisbecker
2011-12-21 2:02 ` [PATCH 2/2 v2] cgroup: Drop task_lock(parent) on cgroup_fork() Frederic Weisbecker
2011-12-21 2:16 ` Li Zefan
2011-12-21 2:48 ` Frederic Weisbecker
2011-12-21 3:16 ` Li Zefan
2011-12-21 17:50 ` Tejun Heo
2011-12-21 17:51 ` Tejun Heo
2011-12-21 17:52 ` Frederic Weisbecker
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=1324432958-20414-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=msb@chromium.org \
--cc=oleg@redhat.com \
--cc=paul@paulmenage.org \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®