From: Matan Peled <chaosite@gmail.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: Tue, 25 Oct 2005 14:04:06 +0200 [thread overview]
Message-ID: <435E1F36.2030108@gmail.com> (raw)
In-Reply-To: <20051024015710.29a02e63@werewolf.able.es>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
J.A. Magallon wrote:
> 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".
I don't know why, but 'du' seems to be doing a better job.
chaosite@kaitou ~ $ du /proc/kcore --block-size=1M
1024 /proc/kcore
chaosite@kaitou ~ $ echo $(($(stat -c %s /proc/kcore) / 1024 / 1024))
1023
- --
[Name ] :: [Matan I. Peled ]
[Location ] :: [Israel ]
[Public Key] :: [0xD6F42CA5 ]
[Keyserver ] :: [keyserver.kjsl.com]
encrypted/signed plain text preferred
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDXh82A7Qvptb0LKURApoUAKCVpGY9BlyD2SwN1aPy566ptf5DGwCdExco
emsyr109/L8ls6Czh7mv45Q=
=jRrP
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-10-25 12:02 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
2005-10-25 12:04 ` Matan Peled [this message]
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=435E1F36.2030108@gmail.com \
--to=chaosite@gmail.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.