From: Vasya Boytsov <vasiliy.boytsov@phystech.edu>
To: musl@lists.openwall.com
Subject: Re: New malloc - first preview
Date: Fri, 29 Nov 2019 09:37:15 +0300 [thread overview]
Message-ID: <CANtPb7bY_uMMwZ26zQ88gFV6eQwg8GHEdj4pdmDL1DVhx3c4rw@mail.gmail.com> (raw)
In-Reply-To: <20191128222211.GO16318@brightrain.aerifal.cx>
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@libc.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
next prev parent reply other threads:[~2019-11-29 6:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 17:40 New malloc - intro, motivation & design goals document Rich Felker
2019-11-06 3:46 ` Non-candidate allocator designs, things to learn from them Rich Felker
2019-11-06 10:06 ` Florian Weimer
2019-11-28 21:56 ` New malloc - first preview Rich Felker
2019-11-28 22:22 ` Rich Felker
2019-11-29 6:37 ` Vasya Boytsov [this message]
2019-11-29 13:55 ` Rich Felker
2019-11-30 5:54 ` Rich Felker
2019-11-29 16:41 ` Roman Yeryomin
2019-11-30 4:49 ` Rich Felker
2019-11-29 19:45 ` Markus Wichmann
2019-11-30 3:15 ` Rich Felker
2019-11-30 22:11 ` Rich Felker
2019-12-06 5:06 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANtPb7bY_uMMwZ26zQ88gFV6eQwg8GHEdj4pdmDL1DVhx3c4rw@mail.gmail.com \
--to=vasiliy.boytsov@phystech.edu \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).