From: Christopher Friedt <chrisfriedt@gmail.com>
To: musl@lists.openwall.com
Subject: Re: malloc implementation survey: omalloc
Date: Mon, 30 Jul 2018 15:34:46 -0400 [thread overview]
Message-ID: <CAF4BF-S5g-LTq=UQ11=M9swTU-8AQtYeLRXkXOjSW19pf3A6ww@mail.gmail.com> (raw)
In-Reply-To: <CAF4BF-QPe6NFrEaYhJOvpZ4=bP8d03g1yMQvK_1As+GNPmAruA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 60 bytes --]
The buddy malloc overhead approaches 3.125% asymptotically.
[-- Attachment #2: Type: text/html, Size: 82 bytes --]
next prev parent reply other threads:[~2018-07-30 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 19:26 Markus Wichmann
2018-07-30 15:09 ` Christopher Friedt
2018-07-30 19:14 ` Christopher Friedt
2018-07-30 19:22 ` Christopher Friedt
2018-07-30 19:34 ` Christopher Friedt [this message]
2018-07-31 7:49 ` Markus Wichmann
2018-07-31 14:25 ` Rich Felker
2018-07-31 14:49 ` Christopher Friedt
2018-07-31 0:47 ` Rich Felker
2018-07-31 1:44 ` Rich Felker
2018-08-30 18:16 ` A. Wilcox
2018-08-30 18:46 ` 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='CAF4BF-S5g-LTq=UQ11=M9swTU-8AQtYeLRXkXOjSW19pf3A6ww@mail.gmail.com' \
--to=chrisfriedt@gmail.com \
--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).