On Thu, Jul 03, 2008 at 02:41:33PM +0100, Daniel P. Berrange wrote:
The OOM testing takes a long time to run. Add in valgrind, and it takes a very very very long time to run. My dev box has 8 cpus though and it'd be nice to use all 8 rather than just 1 to cut the time by a factor of 8. So this patch tweaks the control harness for the OOM testrig so that it can fork off multiple worker processes. Each worker is assigned a number from 1 -> n, and will be responsible for test all allocations failures divisible by their number.
By default it still runs single process, but if you set VIR_TEST_MP=1 then we use sysconf() to get the actual number of online CPUs and fork off one worker per CPU.
eg, so to run the OOM testing with valgrind, parallelized
$ VIR_TEST_MP=1 VIR_TEST_OOM=1 make valgrind
Or to run a test directly
$ VIR_TEST_MP=1 VIR_TEST_OOM=1 valgrind --leak-check=full ./xmconfigtest
haha, sure, go for it :-) ! +1 Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/