From: "Christ, Bryan" <bryan.christ@hp.com>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: Dan Gary <funkychunkymunky@gmail.com>,
linux-c-programming@vger.kernel.org
Subject: Re: max heap usage of a Linux process
Date: Mon, 13 Nov 2006 10:12:58 -0600 [thread overview]
Message-ID: <1163434378.13061.10.camel@tuxdev.americas.hpqcorp.net> (raw)
In-Reply-To: <d9def9db0611130759g549bc449i76c2b5e9bff09b3f@mail.gmail.com>
If you want to know how much you are using, look at uordblks not
ordblks. The allocator dishes out memory in chunks (not the same has
bytes requested via malloc() so there will most often be some
difference).
See the GNU documentation at:
http://www.gnu.org/software/libc/manual/html_node/Statistics-of-Malloc.html#Statistics-of-Malloc
BTW, I think the chunk size will always be a multiple of page size (see
the man pages for getpagesize() -- but I haven't give it any thorough
investigation). Perhaps someone on this list can confirm.
On Mon, 2006-11-13 at 16:59 +0100, Markus Rechberger wrote:
> Hi,
>
> On 11/13/06, Dan Gary <funkychunkymunky@gmail.com> wrote:
> > unless parent is asking about malloc'd space, then mallinfo() or
> > malloc_stats() might be what they're looking for, memory profiling the
> > manual way, gotta love it
> >
>
> interesting didn't know that..
>
> though now I have a question about it ..
>
> #include <malloc.h>
> #include <stdio.h>
> #include <stdlib.h>
>
> int main(){
> char *foo;
> printf("total free space: %d\n",mallinfo().fordblks);
> foo=malloc(500000);
> if(foo){
> printf("successfully allocated!\n");
> } else {
> printf("error allocating!\n");
> }
> printf("arena: %d\n",mallinfo().arena);
> printf("ordblks: %d\n",mallinfo().ordblks);
> printf("max total allocated space: %d\n",mallinfo().usmblks);
> printf("total allocated space: %d\n",mallinfo().uordblks);
> printf("total free space: %d\n",mallinfo().fordblks);
>
> return 0;
> }
>
> outputs:
> total free space: 0
> successfully allocated!
> arena: 0
> ordblks: 1
> max total allocated space: 0
> total allocated space: 0
> total free space: 0
>
> If I allocate 50000bytes then it outputs:
> total free space: 0
> successfully allocated!
> arena: 184320
> ordblks: 1
> max total allocated space: 0
> total allocated space: 50008
> total free space: 134312
>
> does anyone have an explanation for that?
>
> Markus
> -
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-11-13 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 13:31 max heap usage of a Linux process Prasanta Sadhukhan
2006-11-13 14:09 ` Markus Rechberger
2006-11-13 15:39 ` Dan Gary
2006-11-13 15:59 ` Markus Rechberger
2006-11-13 16:12 ` Christ, Bryan [this message]
2006-11-14 6:26 ` Prasanta Sadhukhan
2006-11-14 10:57 ` Glynn Clements
2006-11-14 11:30 ` Prasanta Sadhukhan
2006-11-14 14:36 ` Glynn Clements
2006-11-14 11:39 ` Al Boldi
2006-11-14 15:19 ` Christ, Bryan
2006-11-13 15:30 ` Christ, Bryan
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=1163434378.13061.10.camel@tuxdev.americas.hpqcorp.net \
--to=bryan.christ@hp.com \
--cc=funkychunkymunky@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=mrechberger@gmail.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 NNTP newsgroup(s).