From: "Rémi Colinet" <remi.colinet@wanadoo.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2 : size of /proc/kcore is different from RAM size.
Date: Sun, 10 Aug 2003 23:20:03 +0200 [thread overview]
Message-ID: <3F36B703.90405@wanadoo.fr> (raw)
In-Reply-To: 3F36A74B.6090200@wanadoo.fr
Rémi Colinet wrote:
> Hi,
>
> I have noticed that the /proc/kcore file has a different size (1Go)
> compared with the available memory of my box (640Mo).
>
> [root@tigre01 kernel]# dmesg | grep Memory
> Memory: 643148k/655360k available (2331k kernel code, 11424k reserved,
> 730k data, 348k init, 0k highmem)
>
> [root@tigre01 proc]# ls -l /proc | grep kcore
> -r-------- 1 root root 1073692672 Aug 10 21:43 kcore
> [root@tigre01 proc]#
>
> Is it a bug or just a new behaviour of the /proc/kcore?
>
> Regards,
> Rémi
It's ok with 2.6.0-test3-mm1.
Remi
next prev parent reply other threads:[~2003-08-10 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 20:12 2.6.0-test2 : size of /proc/kcore is different from RAM size Rémi Colinet
2003-08-10 21:20 ` Rémi Colinet [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-13 17:00 Luck, Tony
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=3F36B703.90405@wanadoo.fr \
--to=remi.colinet@wanadoo.fr \
--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