linux-kernel - Re: [Use cpuops V1 10/11] fs: Use this_cpu

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]

Date:	Tue, 07 Dec 2010 16:16:04 +0100
From:	Tejun Heo <tj@...nel.org>
To:	Christoph Lameter <cl@...ux.com>
CC:	akpm@...ux-foundation.org, Wu Fengguang <fengguang.wu@...el.com>,
	Christoph Hellwig <hch@....de>,
	Pekka Enberg <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org,
	Eric Dumazet <eric.dumazet@...il.com>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: [Use cpuops V1 10/11] fs: Use this_cpu_xx operations in buffer.c

On 12/06/2010 06:16 PM, Christoph Lameter wrote:
> Optimize various per cpu area operations through the new this cpu
> operations. These operations avoid address calculations through the use
> of segment prefixes avoid multiple memory references through RMW
> instructions etc.
> 
> Reduces code size:
> 
> Before:
> 
> christoph@...ux-2.6$ size fs/buffer.o
>    text	   data	    bss	    dec	    hex	filename
>   19169	     80	     28	  19277	   4b4d	fs/buffer.o
> 
> After:
> 
> christoph@...ux-2.6$ size fs/buffer.o
>    text	   data	    bss	    dec	    hex	filename
>   19138	     80	     28	  19246	   4b2e	fs/buffer.o
> 
> V3->V4:
> 	- Move the use of this_cpu_inc_return into a later patch so that
> 	  this one can go in without percpu infrastructure changes.
> 
> Cc: Wu Fengguang <fengguang.wu@...el.com>
> Cc: Christoph Hellwig <hch@....de>
> Signed-off-by: Christoph Lameter <cl@...ux.com>

applied 10 and 11.

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