From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: "zack@owlfolio.org" <zack@owlfolio.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: 'GNU C Library' <libc-alpha@sourceware.org>
Subject: [PATCH] malloc: Use correct C11 atomics for fastbin
Date: Tue, 6 Dec 2022 15:04:49 +0000 [thread overview]
Message-ID: <PAWPR08MB8982ADFFC266F0473A642E80831B9@PAWPR08MB8982.eurprd08.prod.outlook.com> (raw)
Hi,
>> Modern allocators are not only much faster than GLIBC in their default settings
>>> but also have lower memory usage. The two best allocators seem to be mimalloc
>>> and jemalloc.
>>
>>
>> Do they have compatible license so we can just import/adapt the code?
>
> Per https://github.com/jemalloc/jemalloc/blob/dev/COPYING jemalloc is 2-clause BSD.
> I don't know where to find mimalloc off the top of my head.
Mimalloc uses the MIT license: https://github.com/microsoft/mimalloc/blob/master/LICENSE
Cheers,
Wilco
next reply other threads:[~2022-12-06 15:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 15:04 Wilco Dijkstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-21 16:09 Wilco Dijkstra
2022-11-21 16:18 ` Florian Weimer
2022-11-21 16:55 ` Wilco Dijkstra
2022-11-21 16:56 ` Wilco Dijkstra
2022-11-21 17:00 ` Florian Weimer
2022-12-02 5:11 ` DJ Delorie
2022-12-02 6:36 ` Florian Weimer
2022-12-02 10:56 ` Wilco Dijkstra
2022-12-02 11:24 ` Florian Weimer
2022-12-02 12:02 ` Wilco Dijkstra
2022-12-02 18:55 ` DJ Delorie
2022-12-05 18:39 ` Zack Weinberg
2022-12-06 16:19 ` DJ Delorie
2022-12-12 3:35 ` Zack Weinberg
2022-12-12 11:57 ` Florian Weimer
2022-12-12 11:56 ` Florian Weimer
2022-12-06 13:29 ` Wilco Dijkstra
2022-12-06 13:37 ` Adhemerval Zanella Netto
2022-12-06 14:31 ` Zack Weinberg
2022-12-06 16:23 ` DJ Delorie
2022-12-15 15:43 ` Wilco Dijkstra
2022-12-02 18:55 ` DJ Delorie
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=PAWPR08MB8982ADFFC266F0473A642E80831B9@PAWPR08MB8982.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=zack@owlfolio.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).