This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] tst-malloc-thread-exit: run less aggressively
- From: Florian Weimer <fweimer at redhat dot com>
- To: Chris Metcalf <cmetcalf at ezchip dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Tue, 19 Jan 2016 21:04:44 +0100
- Subject: Re: [PATCH] tst-malloc-thread-exit: run less aggressively
- Authentication-results: sourceware.org; auth=none
- References: <1453233538-24029-1-git-send-email-cmetcalf at ezchip dot com>
On 01/19/2016 08:58 PM, Chris Metcalf wrote:
> On a 64-bit machine, the previous code would run up to
> 5 x 8 x NPROCS threads, or 2,880 threads on a 72-core TILE-Gx.
> But since typically userspace runs with an RLIMIT_NPROC value
> of 1024, the test will fail on such a machine. Instead, bound
> the outer thread count to 200, rather than 8 x NPROCS, so that
> the total number of threads created is max 1000. This may still
> be a little risky when running in a "make -j check" context but
> should at least pass when run separately to confirm a FAIL.
I posted a patch due to similar issues:
<https://sourceware.org/ml/libc-alpha/2015-12/msg00537.html>
This change will bring down the run time considerably.
> Can I push this for 2.23? It fixes a test failure for tilegx.
Not just there.
I wasn't aware of the thread count limit. I can post a patch tomorrow
which uses mallopt to reduce the arena count, then we should be able to
run this test with just 8 threads (but I will have to verify it still
triggers the original failure).
Florian