[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-threads
Subject:    [Bug 200138] [PATCH] Fixed sthread-specific array allocation conflict incurred in libthr by some for
From:       bugzilla-noreply () freebsd ! org
Date:       2015-05-13 2:15:08
Message-ID: bug-200138-16-rx4q7Yuq0J () https ! bugs ! freebsd ! org/bugzilla/
[Download RAW message or body]

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.
_______________________________________________
freebsd-threads@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-threads
To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]