From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Carlos O'Donell <carlos@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH 1/2] Add note on MALLOC_MMAP_* environment variables
Date: Mon, 17 Oct 2016 16:16:00 -0000 [thread overview]
Message-ID: <02f5d891-c00c-a376-82e4-168bbb9bbcc7@sourceware.org> (raw)
In-Reply-To: <013af3b4-a6db-dd01-9adf-028ba53daf00@redhat.com>
On Monday 17 October 2016 09:43 PM, Carlos O'Donell wrote:
> On 10/10/2016 01:26 PM, Siddhesh Poyarekar wrote:
>> The mallopt parameters manual does not mention the environment
>> variables that can be used to set these parameters at program startup.
>> Mention those environment variables for completeness.
>
> Please don't get upset with me :-)
Grrr...
> I'm asking you to document the default for these env var tunables.
>
> I think it's valid for users to want to know what value they would have
> had if they _didn't_ set the environment variable.
>
> Throwing our hands up in the air and saying "it's implementation defined"
> isn't very useful IMO.
No I agree that is a good point. I'll work on it based on your comments
on the MALLOC_ARENA_* doc patch, i.e. first describe the GNU allocator
and then use that information to explain the envvars/mallopt params and
also add in defaults.
Siddhesh
next prev parent reply other threads:[~2016-10-17 16:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 17:26 Siddhesh Poyarekar
2016-10-10 17:26 ` [PATCH 2/2] Document the M_ARENA_* mallopt parameters Siddhesh Poyarekar
2016-10-17 14:04 ` [PING][PATCH " Siddhesh Poyarekar
2016-10-17 16:09 ` [PATCH " Carlos O'Donell
2016-10-18 7:15 ` Michael Kerrisk
2016-10-18 10:07 ` Siddhesh Poyarekar
2016-10-18 13:50 ` Michael Kerrisk (man-pages)
2016-10-18 14:30 ` Siddhesh Poyarekar
2016-10-18 16:03 ` Michael Kerrisk (man-pages)
2016-10-18 16:46 ` Siddhesh Poyarekar
2016-10-18 17:18 ` Andreas Schwab
2016-10-19 6:53 ` Michael Kerrisk (man-pages)
2016-10-19 7:09 ` Siddhesh Poyarekar
2016-10-10 17:33 ` [PATCH 1/2] Add note on MALLOC_MMAP_* environment variables DJ Delorie
2016-10-10 17:42 ` Siddhesh Poyarekar
2016-10-11 6:20 ` Michael Kerrisk
2016-10-11 18:19 ` DJ Delorie
2016-10-11 19:03 ` Michael Kerrisk (man-pages)
2016-10-12 11:57 ` Siddhesh Poyarekar
2016-10-17 19:40 ` Carlos O'Donell
2016-10-11 19:35 ` Kalle Olavi Niemitalo
2016-10-17 14:04 ` [PING][PATCH " Siddhesh Poyarekar
2016-10-17 16:13 ` [PATCH " Carlos O'Donell
2016-10-17 16:16 ` Siddhesh Poyarekar [this message]
2016-10-24 14:08 [PATCH 0/2] Malloc manual cleanups Siddhesh Poyarekar
2016-10-24 14:08 ` [PATCH 1/2] Add note on MALLOC_MMAP_* environment variables Siddhesh Poyarekar
2016-10-26 4:18 ` Carlos O'Donell
2016-10-26 7:58 ` Michael Kerrisk
2016-10-26 9:47 ` Siddhesh Poyarekar
2016-10-26 11:26 ` Rical Jasan
2016-10-26 11:30 ` Siddhesh Poyarekar
2016-10-26 12:04 ` Rical Jasan
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=02f5d891-c00c-a376-82e4-168bbb9bbcc7@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.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).