From: Michal Hocko <mhocko@suse.cz>
To: Vladimir Davydov <vdavydov@parallels.com>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH -mm 1/2] memcg: get rid of memcg_create_cache_name
Date: Wed, 7 May 2014 11:51:27 +0200 [thread overview]
Message-ID: <20140507095127.GC9489@dhcp22.suse.cz> (raw)
In-Reply-To: <a4aa62026c10fc709e8bf13542b29cf771381394.1399450112.git.vdavydov@parallels.com>
On Wed 07-05-14 12:15:29, Vladimir Davydov wrote:
> Instead of calling back to memcontrol.c from kmem_cache_create_memcg in
> order to just create the name of a per memcg cache, let's allocate it in
> place. We only need to pass the memcg name to kmem_cache_create_memcg
> for that - everything else can be done in slab_common.c.
>
> Signed-off-by: Vladimir Davydov <vdavydov@parallels.com>
Seems good to me.
I would keep the comment about the static buffer as mentioned below.
Other than that
Acked-by: Michal Hocko <mhocko@suse.cz>
[...]
> -char *memcg_create_cache_name(struct mem_cgroup *memcg,
> - struct kmem_cache *root_cache)
> -{
> - static char *buf;
> -
> - /*
> - * We need a mutex here to protect the shared buffer. Since this is
> - * expected to be called only on cache creation, we can employ the
> - * slab_mutex for that purpose.
> - */
> - lockdep_assert_held(&slab_mutex);
> -
> - if (!buf) {
> - buf = kmalloc(NAME_MAX + 1, GFP_KERNEL);
> - if (!buf)
> - return NULL;
> - }
> -
> - cgroup_name(memcg->css.cgroup, buf, NAME_MAX + 1);
> - return kasprintf(GFP_KERNEL, "%s(%d:%s)", root_cache->name,
> - memcg_cache_id(memcg), buf);
> -}
> -
> int memcg_alloc_cache_params(struct mem_cgroup *memcg, struct kmem_cache *s,
> struct kmem_cache *root_cache)
> {
> @@ -3164,6 +3141,7 @@ void memcg_free_cache_params(struct kmem_cache *s)
> static void memcg_kmem_create_cache(struct mem_cgroup *memcg,
> struct kmem_cache *root_cache)
> {
> + static char *memcg_name_buf;
> struct kmem_cache *cachep;
> int id;
So we are relying on memcg_slab_mutex now, right? Worth a comment I
suppose.
--
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-05-07 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 8:15 Vladimir Davydov
2014-05-07 8:15 ` [PATCH -mm 2/2] memcg: cleanup kmem cache creation/destruction functions naming Vladimir Davydov
2014-05-07 12:45 ` Michal Hocko
2014-05-13 15:05 ` [PATCH -mm v2] " Vladimir Davydov
2014-05-14 9:40 ` Michal Hocko
2014-05-07 9:51 ` Michal Hocko [this message]
2014-05-07 10:45 ` [PATCH -mm 1/2] memcg: get rid of memcg_create_cache_name Vladimir Davydov
2014-05-07 11:19 ` Michal Hocko
2014-05-07 20:53 ` Andrew Morton
2014-05-08 7:08 ` Vladimir Davydov
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=20140507095127.GC9489@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