linux-kernel - Re: [PATCH v2 03/10] slab: move up code to get kmem_cache_node in free

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: <alpine.DEB.2.10.1405080850420.22626@gentwo.org>
Date:	Thu, 8 May 2014 08:51:40 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	David Rientjes <rientjes@...gle.com>
cc:	George Spelvin <linux@...izon.com>, iamjoonsoo.kim@....com,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v2 03/10] slab: move up code to get kmem_cache_node in
 free_block()

On Wed, 7 May 2014, David Rientjes wrote:

> > @@ -3362,17 +3359,12 @@ static void free_block(struct kmem_cache *cachep, void **objpp, int nr_objects,
> >  		       int node)
> >  {
> >  	int i;
> > -	struct kmem_cache_node *n;
> > +	struct kmem_cache_node *n = cachep->node[node];
> >
> >  	for (i = 0; i < nr_objects; i++) {
> > -		void *objp;
> > -		struct page *page;
> > -
> > -		clear_obj_pfmemalloc(&objpp[i]);
> > -		objp = objpp[i];
> > +		void *objp = clear_obj_pfmemalloc(&objpp[i]);
> > +		struct page *page = virt_to_head_page(objp);
> >
> > -		page = virt_to_head_page(objp);
> > -		n = cachep->node[node];
> >  		list_del(&page->lru);
> >  		check_spinlock_acquired_node(cachep, node);
> >  		slab_put_obj(cachep, page, objp, node);
>
> I think this unnecessarily obfuscates the code.

It takes the lookup out of the loop. What does the obfuscation?


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