From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] cgroup: remove hierarchy_mutex
Date: Thu, 7 Jun 2012 11:33:02 +0900 [thread overview]
Message-ID: <20120607023302.GH21357@google.com> (raw)
In-Reply-To: <4FCC5792.8010203-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
On Mon, Jun 04, 2012 at 02:37:06PM +0800, Li Zefan wrote:
> It was introduced for memcg to iterate cgroup hierarchy without
> holding cgroup_mutex, but soon after that it was replaced with
> a lockless way in memcg.
>
> No one used hierarchy_mutex since that, so remove it.
>
> Signed-off-by: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Applied to cgroup/for-3.6. Thanks.
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Li Zefan <lizefan@huawei.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Cgroups <cgroups@vger.kernel.org>
Subject: Re: [PATCH] cgroup: remove hierarchy_mutex
Date: Thu, 7 Jun 2012 11:33:02 +0900 [thread overview]
Message-ID: <20120607023302.GH21357@google.com> (raw)
In-Reply-To: <4FCC5792.8010203@huawei.com>
On Mon, Jun 04, 2012 at 02:37:06PM +0800, Li Zefan wrote:
> It was introduced for memcg to iterate cgroup hierarchy without
> holding cgroup_mutex, but soon after that it was replaced with
> a lockless way in memcg.
>
> No one used hierarchy_mutex since that, so remove it.
>
> Signed-off-by: Li Zefan <lizefan@huawei.com>
Applied to cgroup/for-3.6. Thanks.
--
tejun
next prev parent reply other threads:[~2012-06-07 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 6:37 [PATCH] cgroup: remove hierarchy_mutex Li Zefan
2012-06-04 6:37 ` Li Zefan
[not found] ` <4FCC5792.8010203-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2012-06-07 2:33 ` Tejun Heo [this message]
2012-06-07 2:33 ` 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=20120607023302.GH21357@google.com \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.