[PATCH] Do not scale NPTL tests with available number of CPUs

Carlos O'Donell carlos@redhat.com
Wed Aug 30 14:51:00 GMT 2017


On 08/30/2017 07:44 AM, Florian Weimer wrote:
> On very large multi-processor systems, creating hundreds of threads
> runs into a test time out.  The tests do not seem to benefit from
> massive over-scheduling.
> 
> 2017-08-30  Florian Weimer  <fweimer@redhat.com>
> 
> 	Do not scale NPTL tests with available number of CPUs.
> 	* nptl/tst-cond16.c (count): Sett to constant value of 8.
> 	* nptl/tst-cond18.c (count): Likewise.

The patch looks good to me.

What I would *like* to see here is a support override for this.

An API which passes in a default, 8 cpus, and the output is 8 cpus,
so long as the support library doesn't override the number of cpus
to use.

This way I can re-run the entire testsuite with maximum number of
cpus for tests that claim such scalability.

-- 
Cheers,
Carlos.



More information about the Libc-alpha mailing list