All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Smietanowski <stesmi@stesmi.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: jonathan@jonmasters.org, jonmasters@gmail.com,
	"Linux-Kernel," <linux-kernel@vger.kernel.org>
Subject: Re: /proc/kcore size incorrect ?
Date: Mon, 24 Oct 2005 16:19:42 +0200	[thread overview]
Message-ID: <435CED7E.6000402@stesmi.com> (raw)
In-Reply-To: <20051024015710.29a02e63@werewolf.able.es>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi.

> I expected /proc/kcore to give the size of your installed memory, with
> the reserved BIOS areas just not accesible, but it looks like it already
> has them discounted, so gives 1022 Mb.
> 
> It looks really silly to have a motd say "wellcome to this box, it has
> 2 xeons and 1022 Mb of RAM".

Then round it on 32MiB boundary? 128MiB boundary?

I did something else that "needed" the size of the memory installed
and that's how I did.

( I have an install script which I run at the end of an installation
  of a system that does a lot of stuff the distro doesn't and one
  of the things it does is simply to take the size of the memory
  rounded up, multiply by 2 and then create a swapfile in a specified
  location. )

// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFDXO1+Brn2kJu9P78RAp6aAJ9VXDLkwGHkewZtyIsajlcMugsuUwCdHKB6
da0LD9u6SHA4iL/OfHr6dD8=
=3DXl
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2005-10-24 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-23 21:58 /proc/kcore size incorrect ? J.A. Magallon
2005-10-23 23:13 ` Jon Masters
2005-10-23 23:57   ` J.A. Magallon
2005-10-24 12:02     ` Jon Masters
2005-10-24 14:19     ` Stefan Smietanowski [this message]
2005-10-25 12:04     ` Matan Peled
2005-10-25 13:37       ` Brian Waite
2005-10-25 16:02     ` /proc/kcore size incorrect ? (OT) Eric Piel
2005-10-25 16:06       ` J.A. Magallon
2005-10-25 18:04         ` Tony Luck

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=435CED7E.6000402@stesmi.com \
    --to=stesmi@stesmi.com \
    --cc=jamagallon@able.es \
    --cc=jonathan@jonmasters.org \
    --cc=jonmasters@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.