From: Rical Jasan <ricaljasan@pacific.net>
To: siddhesh@sourceware.org
Cc: "Carlos O'Donell" <carlos@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH 1/2] Add note on MALLOC_MMAP_* environment variables
Date: Wed, 26 Oct 2016 12:04:00 -0000 [thread overview]
Message-ID: <29b42fbc-e5c9-bd8b-a004-007c025d827a@pacific.net> (raw)
In-Reply-To: <7d130361-6bc1-dff6-f9c0-bdd51fc43fc3@sourceware.org>
On 10/26/2016 04:30 AM, Siddhesh Poyarekar wrote:
> On Wednesday 26 October 2016 04:56 PM, Rical Jasan wrote:
>> On 10/25/2016 09:15 PM, Carlos O'Donell wrote:
>>>>> +If this parameter is not set, the default value is set as 128 KB and the
>>> Should this be 128KiB?
>>
>> I don't think binary computers count with 10 fingers. At any rate, we
>> don't have any ibi's AFAICS:
>>
>> $ grep -Pi '\d[kmgt]i?b\b' manual/*.texi
>
> It's the other way around AFAIK, i.e. KiB == 1024 and KB == 1000. Looks
> like there are references to kB in code comments, so I'm fine with
> changing it to that, or if you want to be absolutely clear, I could just
> make it 131072 bytes ;)
As unambiguous as possible is best, so if you could fix the 2147483648-
and 4294967296-byte references too, that'd be great. lol
Rical
next prev parent reply other threads:[~2016-10-26 12:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 14:08 [PATCH 0/2] Malloc manual cleanups Siddhesh Poyarekar
2016-10-24 14:08 ` [PATCH 2/2] Document the M_ARENA_* mallopt parameters Siddhesh Poyarekar
2016-10-25 7:51 ` Rical Jasan
2016-10-25 21:55 ` DJ Delorie
2016-10-26 5:42 ` 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-10 17:26 Siddhesh Poyarekar
2016-10-10 17:33 ` 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 16:13 ` Carlos O'Donell
2016-10-17 16:16 ` Siddhesh Poyarekar
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=29b42fbc-e5c9-bd8b-a004-007c025d827a@pacific.net \
--to=ricaljasan@pacific.net \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@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).