linux-kernel - Re: [PATCH 3/9] rcu: Cleanup rcu_init

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:	Sat, 7 Mar 2015 18:59:54 +0000
From:	Alexander Gordeev <agordeev@...hat.com>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/9] rcu: Cleanup rcu_init_geometry() code and arithmetics

On Sat, Mar 07, 2015 at 10:08:21AM -0800, Paul E. McKenney wrote:
> The rest of this series looks promising, but I do have to ask...  How have
> you tested these?  The most straightforward approach would be to find

I tried trees with 1,2 and 3 levels on a 160-CPU machine + dozens of kernel
builds with 'make -j160'. I feel bit guilty I did not try the corner case
with 4 levels, but run-time-wise it is not really differ from what I done.

Do you expect the below is a better option?

> a KVM-capable system with at least 16 CPUs and type the following from
> the top-level directory:
> 
> sh tools/testing/selftests/rcutorture/bin/kvm.sh --cpus 34 --duration 5
> 
> This will do a series of 16 build-boot-test cycles with various configs
> (including various rcu_node tree shapes), and print a summary of the
> outcome at the end.
> 
> For these sorts of changes, I usually also do some user-level testing.

-- 
Regards,
Alexander Gordeev
agordeev@...hat.com
--
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/