public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "N. Varadarajan" <varadhu_n@techmas.hcltech.com>
To: kernel Linux <linux-kernel@vger.kernel.org>,
	Vasu Varma P V <pvvvarma@techmas.hcltech.com>
Subject: [Fwd: Re: Total RAM in the system]
Date: Wed, 11 Jul 2001 14:16:38 +0530	[thread overview]
Message-ID: <3B4C126E.8085BDD@techmas.hcltech.com> (raw)

hi Mike,
i tried that already on a 2.2.18 kernel and
num_physpages is not
exported. num_physpages does not contain the
actual RAM present
in the system.

i booted up my linux with command line parameter
mem=32M,
but my machine actually had 128M RAM. and from KDB
i inspected
num_physpages which showed me only 32M

thanx

Mike Galbraith wrote:
> 
> On Wed, 11 Jul 2001, N. Varadarajan wrote:
> 
> > Hi,
> > Is there a way to know the amount of physical RAM
> > present in the system from a loadable kernel
> > module
> 
> Yes.. num_physpages is an exported symbol.
> 
>         -Mike

                 reply	other threads:[~2001-07-11  8:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B4C126E.8085BDD@techmas.hcltech.com \
    --to=varadhu_n@techmas.hcltech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pvvvarma@techmas.hcltech.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