From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Re: Removing sbrk and brk
Date: Fri, 3 Jan 2014 12:33:01 -0500 [thread overview]
Message-ID: <20140103173301.GU24286@brightrain.aerifal.cx> (raw)
In-Reply-To: <loom.20140103T124809-643@post.gmane.org>
On Fri, Jan 03, 2014 at 11:51:32AM +0000, Thorsten Glaser wrote:
> Rich Felker <dalias <at> aerifal.cx> writes:
>
> > sbrk may be re-added sometime after 1.0 if malloc is changed to no
> > longer use the brk (option 5 above).
>
> You may want to import omalloc (based on mmap malloc, written from
> scratch by Otto Moerbeek) with lots of security features:
This discussion is about improving one aspect of malloc, not replacing
it with a third-party implementation. The reason musl is significantly
smaller and more maintainable than glibc and uclibc is that it's not a
hodge-podge of copy-and-paste from various legacy code. I suspect
omalloc is considerably higher quality than a lot of the things those
two implementations copied, but from casual inspection, it doesn't
look anywhere near as small or high-performance as musl's.
The actual motivation for moving to mmap in malloc is twofold:
preventing allocation failure when expansion of the brk is blocked by
an inconveniently-placed mapping, and unifying an idea I have in mind
for actually returning unneeded commit charge (right now, musl returns
unneeded physical memory but not commit charge).
> http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libc/stdlib/malloc.c
> http://www.openbsd.org/cgi-bin/man.cgi?query=malloc
>
> It does assume that mmap() is randomised and NULs the result.
If so, this is a rather odd (incorrect) assumption and results in
highly suboptimal behavior (O(n) malloc in place of O(1), where n is
the size of the allocation).
Rich
next prev parent reply other threads:[~2014-01-03 17:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 23:40 Rich Felker
2013-12-22 2:15 ` Luca Barbato
2013-12-22 17:58 ` Richard Pennington
2013-12-22 18:21 ` Luca Barbato
2013-12-22 18:48 ` Szabolcs Nagy
2013-12-22 21:55 ` Christian Neukirchen
2013-12-23 4:46 ` Rich Felker
2014-01-02 22:03 ` Rich Felker
2014-01-03 11:51 ` Thorsten Glaser
2014-01-03 12:59 ` Daniel Cegiełka
2014-01-03 17:33 ` Rich Felker [this message]
2014-01-03 18:19 ` Rich Felker
2014-01-03 19:03 ` Rich Felker
2014-01-06 14:51 ` Thorsten Glaser
2014-01-06 22:40 ` Rich Felker
2014-01-07 9:43 ` Thorsten Glaser
2014-01-07 16:06 ` Rich Felker
2014-01-07 22:00 ` Rich Felker
2014-02-21 16:03 ` Daniel Cegiełka
2014-02-21 16:36 ` Szabolcs Nagy
2014-02-21 16:47 ` Daniel Cegiełka
2014-02-21 17:09 ` Rich Felker
2014-02-21 22:34 ` Daniel Cegiełka
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=20140103173301.GU24286@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).