This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: malloc_stats(3) man page for review
- From: KOSAKI Motohiro <kosaki dot motohiro at gmail dot com>
- To: mtk dot manpages at gmail dot com
- Cc: linux-man <linux-man at vger dot kernel dot org>, libc-alpha at sourceware dot org
- Date: Sat, 5 May 2012 17:13:35 -0400
- Subject: Re: malloc_stats(3) man page for review
- References: <CAKgNAkiC4Qb-yBoEf1mmSBcUFuH3yB0OT6Vvni5z_Lci5=6eSA@mail.gmail.com>
Hi
> .B void malloc_stats(void);
> .SH DESCRIPTION
> The
> .BR malloc_stats ()
> function prints (on standard error) statistics about memory allocated by
> .BR malloc (3)
> and related functions.
> For each arena (allocation area), this function prints
> the total amount of memory allocated by means other than
> .BR mmap (2)
If I understand correctly, A chunk that allocated by mmap (i.e.
IS_MMAPD marked one)
doesn't belong to arena. iow, chunk_for_arena() don't work for mmaped
chunk. then,
For each arena (allocation area), this function prints
the total amount of memory.
is enough.
> and the total number of bytes consumed by in-use allocations.
> (These two values correspond to the
> .I arena
> and
> .I uordblks
> fields retrieved by
> .BR mallinfo (3).)
> In addition,
> the function prints the sum of these two statistics for all arenas,
> and the maximum number of blocks and bytes that were ever simultaneously
> allocated using
> .BR mmap (2).
>
If I understand correctly, this function output "Total (incl.
mmap):\n" header, but
"system bytes" and "in use bytes" don't include mmaped chunk. So, It would be
nice if a bug section describe it.
But I'm not an expert on this area. Please don't 100% trust me.