Date: Wed, 13 May 2015 02:15:08 +0000 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 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200138-16-rx4q7Yuq0J>