Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 May 2015 21:40:34 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-threads@FreeBSD.org
Subject:   [Bug 200138] [PATCH] Fixed per-thread 'specific' array allocation conflict incurred in libthr by some foreign malloc libraries
Message-ID:  <bug-200138-16-FODTXv2878@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200138-16@https.bugs.freebsd.org/bugzilla/>
References:  <bug-200138-16@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200138

--- Comment #19 from yuri@rawbw.com ---
Ideally everything in libthr that is fixed-sized should be allocated with the
single mmap, I think. But this is apparently not the case.

In my process, I see that 0x20000-sized block is always mmapped per-thread.
Must be something google tcmalloc is doing. I first thought this is what libthr
was doing.

But for the time being, we need the solution, so commit your patch making
struct pthread and keys live together.

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200138-16-FODTXv2878>