linux-kernel - Re: [PATCH 0/7] rcu: optimize RCU trace on the huge platform

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-next>] [day] [month] [year] [list]

Message-ID: <20120928175301.GC2498@linux.vnet.ibm.com>
Date:	Fri, 28 Sep 2012 10:53:01 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Michael Wang <wangyun@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, dipankar@...ibm.com
Subject: Re: [PATCH 0/7] rcu: optimize RCU trace on the huge platform

On Thu, Sep 20, 2012 at 08:51:01AM +0800, Michael Wang wrote:
> This patch set optimize the RCU trace to make it perform better on the
> platform with thousands of cpus.
> 
> The optimization including:
> 	-- the cpu info will be separated by each flavor of rcu.
> 	-- implement the 'cpu units sequence reading' to avoid losing data.
> 
> Michael Wang (7):
> 	[PATCH 1/7] rcu: create directory for each flavor of rcu
> 	[PATCH 2/7] rcu: fundamental facility for 'cpu units sequence reading'
> 	[PATCH 3/7] rcu: optimize the 'rcudata' for RCU trace
> 	[PATCH 4/7] rcu: optimize the 'rcudata.csv' for RCU trace
> 	[PATCH 5/7] rcu: optimize the 'rcu_pending' for RCU trace
> 	[PATCH 6/7] rcu: replace the old interface with the new one
> 	[PATCH 7/7] rcu: remove the interface "rcudata.csv"
> 
> Signed-off-by: Michael Wang <wangyun@...ux.vnet.ibm.com>
> ---
>  b/kernel/rcutree_trace.c |    8 +
>  kernel/rcutree_trace.c   |  368 ++++++++++++++++++++---------------------------
>  2 files changed, 170 insertions(+), 206 deletions(-)

Queued for 3.8, thank you Michael!

							Thanx, Paul

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