[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANtPb7bY_uMMwZ26zQ88gFV6eQwg8GHEdj4pdmDL1DVhx3c4rw@mail.gmail.com>
Date: Fri, 29 Nov 2019 09:37:15 +0300
From: Vasya Boytsov <vasiliy.boytsov@...stech.edu>
To: musl@...ts.openwall.com
Subject: Re: New malloc - first preview
Is your malloc implementation any better than
https://github.com/microsoft/mimalloc?
AFAIK one can use mimalloc in their projects as it has compatible license.
the only thing that bothers is that it is done by Microsoft research.
On 11/29/19, Rich Felker <dalias@...c.org> wrote:
> On Thu, Nov 28, 2019 at 04:56:42PM -0500, Rich Felker wrote:
>> Work on the new malloc is well underway, and I have a draft version
>> now public at:
>>
>> https://github.com/richfelker/mallocng-draft
>>
>> Some highlights:
>>
>> - Smallest size-class now has 12 of 16 bytes usable for storage,
>> compared to 8 of 16 (32-bit archs) or 16 of 32 (64-bit archs) with
>> the old malloc, plus 1.5 bytes (32-bit) or 2.5 bytes (64-bit) of
>> out-of-band metadata. This overhead (5.5 or 6.5 bytes per
>> allocation) is uniform across all sizes.
>
> Make that 6 or 7 since there's also a 16-byte (counting alignment,
> which is most of it) group header that imposes 0.5 bytes of overhead
> per slot for a full-length 32-slot group.
>
> Rich
>
--
Respectfully,
Boytsov Vasya
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
