This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] Do not scale NPTL tests with available number of CPUs
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Florian Weimer <fweimer at redhat dot com>, libc-alpha at sourceware dot org
- Date: Wed, 30 Aug 2017 09:51:39 -0500
- Subject: Re: [PATCH] Do not scale NPTL tests with available number of CPUs
- Authentication-results: sourceware.org; auth=none
- References: <20170830124448.87C7741BE92E8@oldenburg.str.redhat.com>
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 <firstname.lastname@example.org>
> 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
This way I can re-run the entire testsuite with maximum number of
cpus for tests that claim such scalability.