From: "J . A . Magallon" <jamagallon@able.es>
To: "Martin . Knoblauch" <Martin.Knoblauch@TeraPort.de>
Cc: "linux-kernel @ vger . kernel . org" <linux-kernel@vger.kernel.org>
Subject: Re: Size of /proc/kcore growing over time ?
Date: Sat, 12 May 2001 00:35:34 +0200 [thread overview]
Message-ID: <20010512003534.A1060@werewolf.able.es> (raw)
In-Reply-To: <3AFBE5BF.5865B0CA@TeraPort.de>
In-Reply-To: <3AFBE5BF.5865B0CA@TeraPort.de>; from Martin.Knoblauch@TeraPort.de on Fri, May 11, 2001 at 15:14:39 +0200
On 05.11 Martin.Knoblauch wrote:
>
> I ask, because I thought the size of kproc could be used to determine
> the amount of physical memory. If this assumption is wrong, is there
> another way to achive the goal?
>
#include <sys/sysinfo.h> // for get_phys_pages()
#include <unistd.h> // for getpagesize()
ram = get_phys_pages()*getpagesize();
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Linux Mandrake release 8.1 (Cooker) for i586
Linux werewolf 2.4.4-ac6 #1 SMP Wed May 9 14:28:00 CEST 2001 i686
next prev parent reply other threads:[~2001-05-11 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 13:14 Size of /proc/kcore growing over time ? Martin.Knoblauch
2001-05-11 22:35 ` J . A . Magallon [this message]
2001-05-14 6:37 ` Martin.Knoblauch
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=20010512003534.A1060@werewolf.able.es \
--to=jamagallon@able.es \
--cc=Martin.Knoblauch@TeraPort.de \
--cc=linux-kernel@vger.kernel.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