From owner-freebsd-threads@FreeBSD.ORG  Wed May 13 02:15:08 2015
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4A444E00
 for <freebsd-threads@FreeBSD.org>; Wed, 13 May 2015 02:15:08 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 33BBE17DF
 for <freebsd-threads@FreeBSD.org>; Wed, 13 May 2015 02:15:08 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4D2F8ho033568
 for <freebsd-threads@FreeBSD.org>; Wed, 13 May 2015 02:15:08 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-threads@FreeBSD.org
Subject: [Bug 200138] [PATCH] Fixed sthread-specific array allocation
 conflict incurred in libthr by some foreign malloc libraries
Date: Wed, 13 May 2015 02:15:08 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: threads
X-Bugzilla-Version: 10.1-STABLE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: yuri@rawbw.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-200138-16-rx4q7Yuq0J@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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads/>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
 <mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2015 02:15:08 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200138

--- Comment #16 from yuri@rawbw.com ---
The mmap patch works, but with his patch every process will have the tiny
separate extra mmapped block per thread. Currently every new thread creates one
extra mmapped block, and this will be the second extra mmapped block. This
doesn't look nice.

Currently every new thread gets its own mmaped block of the size 0x20000 =
131kB. So maybe 2.3% addition isn't that bad, I don't know. Especially that
this memory isn't the real memory allocation unless actually used.

Is it possible to merge them? Adding this 3kB "specific" array block to that
0x2000-sized per-thread block?

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