linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Glauber Costa <glommer@parallels.com>
Cc: Li Zefan <lizefan@huawei.com>, Tejun Heo <tj@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Cgroups <cgroups@vger.kernel.org>,
	linux-mm@kvack.org,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH] memcg: fix memcg_cache_name() to use cgroup_name()
Date: Tue, 26 Mar 2013 09:43:48 +0100	[thread overview]
Message-ID: <20130326084348.GJ2295@dhcp22.suse.cz> (raw)
In-Reply-To: <51515DEE.70105@parallels.com>

On Tue 26-03-13 12:35:58, Glauber Costa wrote:
> >>
> >> I doubt it's a win to add 4K to kernel text size instead of adding
> >> a few extra lines of code... but it's up to you.
> > 
> > I will leave the decision to Glauber. The updated version which uses
> > kmalloc for the static buffer is bellow.
> > 
> I prefer to allocate dynamically here. But although I understand why we
> need to call cgroup_name, I don't understand what is wrong with
> kasprintf if we're going to allocate anyway. It will allocate a string
> just big enough. A PAGE_SIZE'd allocation is a lot more likely to fail.
> 
> Now, if we really want to be smart here, we can do something like what
> I've done for the slub attribute buffers, that can actually have very
> long values.
> 
> allocate a small buffer that will hold 80 % > of the allocations (256
> bytes should be enough for most cache names), and if the string is
> bigger than this, we allocate. Once we allocate, we save it in a static
> pointer and leave it there. The hope here is that we may be able to
> live without ever allocating in many systems.
> 
> > +
> > +	/*
> > +	 * kmem_cache_create_memcg duplicates the given name and
> > +	 * cgroup_name for this name requires RCU context.
> > +	 * This static temporary buffer is used to prevent from
> > +	 * pointless shortliving allocation.
> > +	 */
> The comment is also no longer true if you don't resort to a static buffer.

The buffer _is_ static (read global variable hidden with the function
scope).

> The following (untested) patch implements the idea I outlined above.
> 
> What do you guys think ?

I really do not care which way to fix this.

[...]
> +static struct kmem_cache *kmem_cache_dup(struct mem_cgroup *memcg,
> +					 struct kmem_cache *s)
>  {
> -	char *name;
> -	struct dentry *dentry;
> +	const char *cgname; /* actual cache name */
> +	char *name = NULL; /* actual cache name */
> +	char buf[256]; /* stack buffer for small allocations */
> +	int buf_len;
> +	static char *buf_name; /* pointer to a page, if we ever need */
> +	struct kmem_cache *new;
> +
> +	lockdep_assert_held(&memcg_cache_mutex);
>  
>  	rcu_read_lock();
> -	dentry = rcu_dereference(memcg->css.cgroup->dentry);
> +	cgname = cgroup_name(memcg->css.cgroup);
>  	rcu_read_unlock();

cgname is valid only within RCU read lock AFAIU.

-- 
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>

  reply	other threads:[~2013-03-26  8:43 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21  1:22 Li Zefan
2013-03-21  9:08 ` Michal Hocko
2013-03-21 10:22   ` Michal Hocko
2013-03-22  1:22     ` Li Zefan
2013-03-22  8:07       ` Michal Hocko
2013-03-22  8:17         ` Li Zefan
2013-03-22  8:22           ` Glauber Costa
2013-03-22  9:31             ` Michal Hocko
2013-03-22  9:41               ` Glauber Costa
2013-03-22  9:48                 ` Michal Hocko
2013-03-22 10:03                   ` Glauber Costa
2013-03-22 10:06                     ` Michal Hocko
2013-03-22 10:25                       ` Glauber Costa
2013-03-22 10:56                         ` Michal Hocko
2013-03-24  7:34                           ` Li Zefan
2013-03-25  8:20                             ` Michal Hocko
2013-03-24  7:33               ` Li Zefan
2013-03-25  9:06                 ` Michal Hocko
2013-03-26  7:52                   ` Li Zefan
2013-03-26  8:10                     ` Michal Hocko
2013-03-26  8:35                   ` Glauber Costa
2013-03-26  8:43                     ` Michal Hocko [this message]
2013-03-26  9:02                       ` Glauber Costa
2013-03-27  1:15                         ` Li Zefan
2013-03-27  8:37                           ` Michal Hocko
2013-03-27  8:36 Michal Hocko
2013-03-27 14:58 ` Johannes Weiner
2013-03-27 15:11   ` Michal Hocko
2013-03-27 15:19     ` Glauber Costa
2013-03-27 15:32       ` Michal Hocko
2013-03-27 17:32         ` Michal Hocko
2013-03-28  7:48           ` Michal Hocko
2013-04-02  8:26             ` Michal Hocko
2013-04-03 21:33               ` Tejun Heo
2013-04-04  7:06                 ` Michal Hocko
2013-03-27 15:32     ` Johannes Weiner
2013-03-27 15:47       ` Michal Hocko
2013-03-27 16:15 ` Tejun Heo
2013-03-27 16:19   ` Michal Hocko
2013-03-27 16:21     ` Tejun Heo
2013-03-27 16:27       ` Michal Hocko
2013-03-28  7:22         ` Glauber Costa

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=20130326084348.GJ2295@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=cgroups@vger.kernel.org \
    --cc=glommer@parallels.com \
    --cc=hannes@cmpxchg.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizefan@huawei.com \
    --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