From: Gonzalo Brito Gadeschi <gonzalo.gadeschi@rwth-aachen.de>
To: Rich Felker <dalias@libc.org>
Cc: <musl@lists.openwall.com>
Subject: Re: [feature request] add mallinfo support
Date: Thu, 18 Jan 2018 10:28:35 +0100 [thread overview]
Message-ID: <CAPMgRLSib8gV=5rnjEomY-XfTYZitZ-gHv+7j2Gw7k79Hqpv2g@mail.gmail.com> (raw)
In-Reply-To: <20180117174325.GP1627@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
Thanks for the quick reply.
> Omission of mallinfo is largely intentional.
Makes sense, it would have saved me some time if this
information would be added to the FAQ. I tried to search
the mailing list (or musl website for a bug tracker) without
any luck.
> The API is fundamentally
broken (using type int which cannot represent sizes) and tracking the
information it provides imposes nontrivial costs on the malloc
implementation.
I agree.
> http://www.openwall.com/lists/musl/2013/11/09/2
I went through the thread and could not find the piece of information
that lead to that opinion (maybe I am just generally bad at mailing lists).
Rich Felker (you :D) argued:
> The main reason I'd want to provide a dummy is if
> there are glibc binaries using it. The range of the counters
> is fairly irrelevant; keeping track of the information is prohibitively
> slow anyway since it would have to be synchronized between
> threads on each call to malloc/free. (glibc does some poor
> hack keeping this info per-arena and summarizing it when
mallinfo is called, I think...)
And Szabolcs Nagy just answered:
> i see
That's all I found there.
FWIW I wouldn't mind if mallinfo on musl
would just return a zeroed mallinfo struct,
because I don't even know if the function is
called at all: I just know that the code won't
compile without those symbols.
Arguably, I can do that workaround myself,
so I'll just do that for now.
Thanks again for the quick reply!
Gonzalo
[-- Attachment #2: Type: text/html, Size: 1773 bytes --]
next prev parent reply other threads:[~2018-01-18 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:32 Gonzalo Brito Gadeschi
2018-01-17 17:43 ` Rich Felker
2018-01-18 9:28 ` Gonzalo Brito Gadeschi [this message]
2018-01-18 12:10 ` Dmitry Golovin
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='CAPMgRLSib8gV=5rnjEomY-XfTYZitZ-gHv+7j2Gw7k79Hqpv2g@mail.gmail.com' \
--to=gonzalo.gadeschi@rwth-aachen.de \
--cc=dalias@libc.org \
--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).