linux-kernel - Re: [tip:core/rcu] Revert "rcu: Decrease memory-barrier usage based on semi-formal proof"

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: <4DE07413.5050408@kernel.org>
Date:	Fri, 27 May 2011 21:03:31 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	paulmck@...ux.vnet.ibm.com
CC:	linux-kernel@...r.kernel.org, mingo@...hat.com, hpa@...or.com,
	tglx@...utronix.de, mingo@...e.hu
Subject: Re: [tip:core/rcu] Revert "rcu: Decrease memory-barrier usage based
 on semi-formal proof"

On 05/27/2011 06:04 PM, Paul E. McKenney wrote:
> 
> And, after having repeatedly shot myself in the foot trying to make
> an all-singing all-dancing RCU grace-period latency measurement tool,
> I fell back to simply measuring the RCU grace-period latency during
> the time that memory_dev_init() is running.  This assumes that the
> grace periods are started using synchronize_rcu() -- if they are instead
> being started using call_rcu(), I can adapt to that as well.
> 
[   31.635137] cpu_dev_init done
[   31.635320] Starting RCU latency diagnostics
[   71.605662] Ending RCU latency diagnostics
[   71.605924] memory_dev_init done


Thanks

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