From: William Lovas <wlovas@stwing.upenn.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Determining memory usage?
Date: Sun, 13 Feb 2005 21:05:10 -0500 [thread overview]
Message-ID: <20050214020510.GA10522@force.stwing.upenn.edu> (raw)
In-Reply-To: <20050214124650.69921c71.ocaml-erikd@mega-nerd.com>
On Mon, Feb 14, 2005 at 12:46:50PM +1100, Erik de Castro Lopo wrote:
> Thanks Remi, the heap_words field of the stat record seems to be
> what I want. However sicne that field is in words, I'm looking
> for a way to figure out the word_size (4 vs 8 bytes) so I can
> do a calculation that is correct on 32 and 64 but systems.
>
> Any further clues?
How about the strikingly appropriately named Sys.word_size? :)
cheers,
William
next prev parent reply other threads:[~2005-02-14 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 2:29 Erik de Castro Lopo
2005-02-13 8:31 ` [Caml-list] " Remi Vanicat
2005-02-14 1:46 ` Erik de Castro Lopo
2005-02-14 2:05 ` William Lovas [this message]
2005-02-14 7:03 ` Erik de Castro Lopo
2005-02-16 15:06 ` Damien Doligez
2005-02-14 2:09 ` William D.Neumann
2005-02-14 2:20 ` Jon Harrop
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=20050214020510.GA10522@force.stwing.upenn.edu \
--to=wlovas@stwing.upenn.edu \
--cc=caml-list@inria.fr \
/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).