From: Carlos O'Donell <carlos@redhat.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>, DJ Delorie <dj@redhat.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>, nd <nd@arm.com>
Subject: Re: [PATCH v2] Add malloc micro benchmark
Date: Fri, 5 Jan 2018 06:32:03 -0800 [thread overview]
Message-ID: <b441cd51-6441-d3e7-566e-ce218f39d60b@redhat.com> (raw)
In-Reply-To: <DB6PR0801MB205332F60C0147A0DA956B4F831F0@DB6PR0801MB2053.eurprd08.prod.outlook.com>
On 01/04/2018 05:48 AM, Wilco Dijkstra wrote:
> Carlos O'Donell wrote:
>>
>> Don't use mallopt, please make it a tunable then.
>>
>> The mallopt API already had 2 secret arena options which eventually became
>> so well used they were baked into the API and had to be made public.
>
> Unfortunately tunables are not exported so you can't use them outside of GLIBC:
>
> /build/glibc/benchtests/bench-malloc-simple.o: In function `bench':
> bench-malloc-simple.c:(.text+0x19c): undefined reference to `__tunable_set_val'
> collect2: error: ld returned 1 exit status
Correct, we only have a env-var frontend right now, and the internal API is not
made accessible via GLIBC_PRIVATE.
You have 3 options for tests:
* Use the env vars to adjust test behaviour. Run the tests multiple times.
* Add a new C API frontend, very valuable, but more time consuming.
* Expose the existing internal C API via GLIBC_PRIVATE for testing, and throw
it away later when we get a proper C API frontend.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2018-01-05 14:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 13:51 [PATCH] Add malloc micro benchmark Wilco Dijkstra
2017-12-01 16:13 ` Carlos O'Donell
2017-12-18 15:18 ` Wilco Dijkstra
2017-12-18 16:32 ` Carlos O'Donell
2018-01-02 18:20 ` [PATCH v2] " Wilco Dijkstra
2018-01-02 18:45 ` DJ Delorie
2018-01-03 12:12 ` Wilco Dijkstra
2018-01-03 15:07 ` Carlos O'Donell
2018-01-04 13:48 ` Wilco Dijkstra
2018-01-04 16:37 ` Adhemerval Zanella
2018-01-05 14:32 ` Carlos O'Donell [this message]
2018-01-05 15:50 ` Adhemerval Zanella
2018-01-05 16:17 ` Carlos O'Donell
2018-01-05 16:46 ` Adhemerval Zanella
2018-01-05 17:27 ` Carlos O'Donell
2018-01-05 14:33 ` Carlos O'Donell
2018-01-05 16:28 ` Joseph Myers
2018-01-05 17:26 ` Carlos O'Donell
2018-02-28 12:40 ` Florian Weimer
2018-02-28 14:11 ` Ondřej Bílka
2018-02-28 14:16 ` Florian Weimer
2018-02-28 16:16 ` Carlos O'Donell
2018-02-28 20:17 ` Ondřej Bílka
2018-02-28 16:46 ` Ondřej Bílka
2018-02-28 17:01 ` Wilco Dijkstra
2018-02-28 18:21 ` Carlos O'Donell
2018-02-28 19:56 ` Ondřej Bílka
2018-02-28 21:56 ` DJ Delorie
2018-03-01 11:24 ` Ondřej Bílka
2017-12-18 23:02 ` [PATCH] " DJ Delorie
2017-12-28 14:09 ` Wilco Dijkstra
2017-12-28 19:01 ` 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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b441cd51-6441-d3e7-566e-ce218f39d60b@redhat.com \
--to=carlos@redhat.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.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.
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).