linux-kernel - Re: [PATCH -mm 1/5] quick lookup memcg by ID

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100803140411.cc2c0844.nishimura@mxp.nes.nec.co.jp>
Date:	Tue, 3 Aug 2010 14:04:11 +0900
From:	Daisuke Nishimura <nishimura@....nes.nec.co.jp>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	linux-mm@...ck.org,
	"balbir@...ux.vnet.ibm.com" <balbir@...ux.vnet.ibm.com>,
	vgoyal@...hat.com, m-ikeda@...jp.nec.com, gthelen@...gle.com,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Daisuke Nishimura <nishimura@....nes.nec.co.jp>
Subject: Re: [PATCH -mm 1/5] quick lookup memcg by ID

On Tue, 3 Aug 2010 13:54:13 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote:

> On Tue, 3 Aug 2010 13:51:29 +0900
> Daisuke Nishimura <nishimura@....nes.nec.co.jp> wrote:
> 
> > On Tue, 3 Aug 2010 13:37:23 +0900
> > KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote:
> > 
> > > On Tue, 3 Aug 2010 13:31:09 +0900
> > > Daisuke Nishimura <nishimura@....nes.nec.co.jp> wrote:
> > > 
> > (snip)
> > > > > +/* 0 is unused */
> > > > > +static atomic_t mem_cgroup_num;
> > > > > +#define NR_MEMCG_GROUPS (CONFIG_MEM_CGROUP_MAX_GROUPS + 1)
> > > > > +static struct mem_cgroup *mem_cgroups[NR_MEMCG_GROUPS] __read_mostly;
> > > > > +
> > > > > +static struct mem_cgroup *id_to_memcg(unsigned short id)
> > > > > +{
> > > > > +	/*
> > > > > +	 * This array is set to NULL when mem_cgroup is freed.
> > > > > +	 * IOW, there are no more references && rcu_synchronized().
> > > > > +	 * This lookup-caching is safe.
> > > > > +	 */
> > > > > +	if (unlikely(!mem_cgroups[id])) {
> > > > > +		struct cgroup_subsys_state *css;
> > > > > +
> > > > > +		rcu_read_lock();
> > > > > +		css = css_lookup(&mem_cgroup_subsys, id);
> > > > > +		rcu_read_unlock();
> > > > > +		if (!css)
> > > > > +			return NULL;
> > > > > +		mem_cgroups[id] = container_of(css, struct mem_cgroup, css);
> > > > > +	}
> > > > > +	return mem_cgroups[id];
> > > > > +}
> > > > id_to_memcg() seems to be called under rcu_read_lock() already, so I think
> > > > rcu_read_lock()/unlock() would be unnecessary.
> > > > 
Ah, looking into [2/5], this would not be true necessarily..
So, it might be better to leave as it is.

Sorry for noise.

> > > 
> > > Maybe. I thought about which is better to add
> > > 
> > > 	VM_BUG_ON(!rcu_read_lock_held);
> > > or
> > > 	rcu_read_lock()
> > > 	..
> > > 	rcu_read_unlock()
> > > 
> > > Do you like former ? If so, it's ok to remove rcu-read-lock.
> > > 
> > Yes, I personally like the former.
> 
> ok, will rewrite in that style.
> 
> -Kame
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/