From: Michal Hocko <mhocko@suse.cz>
To: Vladimir Davydov <vdavydov@parallels.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] memcg: remove activate_kmem_mutex
Date: Mon, 20 Oct 2014 20:53:06 +0200 [thread overview]
Message-ID: <20141020185306.GB505@dhcp22.suse.cz> (raw)
In-Reply-To: <1413817889-13915-1-git-send-email-vdavydov@parallels.com>
On Mon 20-10-14 19:11:29, Vladimir Davydov wrote:
> The activate_kmem_mutex is used to serialize memcg.kmem.limit updates,
> but we already serialize them with memcg_limit_mutex so let's remove the
> former.
>
> Signed-off-by: Vladimir Davydov <vdavydov@parallels.com>
Is this the case since bd67314586a3 (memcg, slab: simplify
synchronization scheme)?
Anyway Looks good to me.
Acked-by: Michal Hocko <mhocko@suse.cz>
> ---
> mm/memcontrol.c | 24 +++++-------------------
> 1 file changed, 5 insertions(+), 19 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 3a203c7ec6c7..e957f0c80c6e 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -2618,8 +2618,6 @@ static void commit_charge(struct page *page, struct mem_cgroup *memcg,
> */
> static DEFINE_MUTEX(memcg_slab_mutex);
>
> -static DEFINE_MUTEX(activate_kmem_mutex);
> -
> /*
> * This is a bit cumbersome, but it is rarely used and avoids a backpointer
> * in the memcg_cache_params struct.
> @@ -3756,9 +3754,8 @@ static u64 mem_cgroup_read_u64(struct cgroup_subsys_state *css,
> }
>
> #ifdef CONFIG_MEMCG_KMEM
> -/* should be called with activate_kmem_mutex held */
> -static int __memcg_activate_kmem(struct mem_cgroup *memcg,
> - unsigned long nr_pages)
> +static int memcg_activate_kmem(struct mem_cgroup *memcg,
> + unsigned long nr_pages)
> {
> int err = 0;
> int memcg_id;
> @@ -3820,17 +3817,6 @@ out:
> return err;
> }
>
> -static int memcg_activate_kmem(struct mem_cgroup *memcg,
> - unsigned long nr_pages)
> -{
> - int ret;
> -
> - mutex_lock(&activate_kmem_mutex);
> - ret = __memcg_activate_kmem(memcg, nr_pages);
> - mutex_unlock(&activate_kmem_mutex);
> - return ret;
> -}
> -
> static int memcg_update_kmem_limit(struct mem_cgroup *memcg,
> unsigned long limit)
> {
> @@ -3853,14 +3839,14 @@ static int memcg_propagate_kmem(struct mem_cgroup *memcg)
> if (!parent)
> return 0;
>
> - mutex_lock(&activate_kmem_mutex);
> + mutex_lock(&memcg_limit_mutex);
> /*
> * If the parent cgroup is not kmem-active now, it cannot be activated
> * after this point, because it has at least one child already.
> */
> if (memcg_kmem_is_active(parent))
> - ret = __memcg_activate_kmem(memcg, PAGE_COUNTER_MAX);
> - mutex_unlock(&activate_kmem_mutex);
> + ret = memcg_activate_kmem(memcg, PAGE_COUNTER_MAX);
> + mutex_unlock(&memcg_limit_mutex);
> return ret;
> }
> #else
> --
> 1.7.10.4
>
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-10-20 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 15:11 Vladimir Davydov
2014-10-20 18:21 ` Johannes Weiner
2014-10-20 18:53 ` Michal Hocko [this message]
2014-10-21 6:31 ` Vladimir Davydov
2014-10-21 6:49 ` Michal Hocko
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=20141020185306.GB505@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vdavydov@parallels.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