[haiku-bugs] Re: [Haiku] #13554: Switch system allocator

  • From: "Haiku" <trac@xxxxxxxxxxxx>
  • To: undisclosed-recipients: ;
  • Date: Thu, 16 Apr 2020 02:04:09 -0000

#13554: Switch system allocator
---------------------------------+----------------------------
   Reporter:  waddlesplash       |      Owner:  nobody
       Type:  enhancement        |     Status:  reopened
   Priority:  high               |  Milestone:  R2
  Component:  System/libroot.so  |    Version:  R1/Development
 Resolution:                     |   Keywords:
 Blocked By:                     |   Blocking:
Has a Patch:  0                  |   Platform:  All
---------------------------------+----------------------------
Comment (by waddlesplash):

 Taken mostly from my comment in #15495:

 So, rpmalloc kind of assumes that virtual address space use != physical
 memory reservation, which of course Haiku does so assume, and with good
 reason. It also seems to be designed for "high-performance", i.e. 64-bit
 only where lots of virtual address space waste is fine, and Haiku needs to
 support 32-bit for a while more (and on non-x86, eventually..)

 musl, it seems, is in the process of writing a new allocator, which may be
 a better fit for us: ​https://github.com/richfelker/mallocng-draft

 Original mailing list post:
 ​https://www.openwall.com/lists/musl/2019/11/28/1

 More comments on the design:
 ​https://www.openwall.com/lists/musl/2019/11/29/2 -- note "- compatibility
 with 32-bit address space", and "- elimination of heap size explosion in
 multithreaded apps", which are problems that most modern allocators,
 rpmalloc included, seem to have.
-- 
Ticket URL: <https://dev.haiku-os.org/ticket/13554#comment:15>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.

Other related posts: