public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [PATCH 0/2] Malloc manual cleanups
Date: Mon, 24 Oct 2016 14:08:00 -0000	[thread overview]
Message-ID: <1477318076-22231-1-git-send-email-siddhesh@sourceware.org> (raw)

Here's take 2 of the cleanup of descriptions in the manual description in
malloc.  As suggested in previous review, I have made the following changes:

 - Moved up "Efficiency considerations for malloc" into a new subsection called
   "The GNU allocator" that gives a high level description of the allocator
   design and introduces terms like arenas and chunks.  I did not go into too
   much detail here and have instead pointed interested readers to the wiki page
   DJ wrote.

 - Added default values of all of the mallopt parameters

Siddhesh Poyarekar (2):
  Add note on MALLOC_MMAP_* environment variables
  Document the M_ARENA_* mallopt parameters

 malloc/malloc.c    |   1 -
 manual/memory.texi | 153 ++++++++++++++++++++++++++++++++---------------------
 2 files changed, 93 insertions(+), 61 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-10-24 14:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 14:08 Siddhesh Poyarekar [this message]
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

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=1477318076-22231-1-git-send-email-siddhesh@sourceware.org \
    --to=siddhesh@sourceware.org \
    --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).