linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "Křištof Želechovski" <giecrilj@stegny.2a.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: size of /proc/kcore is not the physical RAM size
Date: Fri, 13 May 2011 09:31:13 -0700	[thread overview]
Message-ID: <m2aaeqzhny.fsf@firstfloor.org> (raw)
In-Reply-To: <201105131440.44747.giecrilj@stegny.2a.pl> ("Křištof	Želechovski"'s message of "Fri, 13 May 2011 14:40:41 +0200")

Křištof Želechovski <giecrilj@stegny.2a.pl> writes:

> [1.] One line summary of the problem:    
> 	Size of /proc/kcore is not the physical RAM size.
> [2.] Full description of the problem/report:
> 	Size of /proc/kcore is not the physical RAM size.

It contains virtual addresses and memory holes, so that's expected.
Not a bug.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

      reply	other threads:[~2011-05-13 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13 12:40 size of /proc/kcore is not the physical RAM size Křištof Želechovski
2011-05-13 16:31 ` Andi Kleen [this message]

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=m2aaeqzhny.fsf@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=giecrilj@stegny.2a.pl \
    --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;
as well as URLs for NNTP newsgroup(s).