From: Jamie Gloudon <jamie.gloudon@gmail.com>
To: Hugh Dickins <hughd@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86_64: wrong DirectMap kB
Date: Mon, 1 Oct 2012 11:43:11 -0400 [thread overview]
Message-ID: <20121001154311.GA2605@darkstar> (raw)
In-Reply-To: <alpine.LSU.2.00.1210010812530.1914@eggly.anvils>
I was also skeptical about DirectMap results added up being less than
MemTotal. I see now, Thanks for the explanation.
Jamie Gloudon
On Mon, Oct 01, 2012 at 08:23:38AM -0700, Hugh Dickins wrote:
> On Mon, 1 Oct 2012, Jamie Gloudon wrote:
> >
> > Interesting. I am able to reproduce the same problem as you using mem=700M, which shows:
> >
> > DirectMap4k: 4096 kB
> > DirectMap2M: 18446744073709547520 kB
> >
> > However, it appears to be normal without the boot parameter:
> >
> > DirectMap4k: 4096 kB
> > DirectMap2M: 15708160 kB
>
> It appears to be normal because the calculations haven't wrapped around,
> but if you compare with 3.4 or before, I think you'll find that it
> still adds up to too little.
>
> >
> > What does your output looks like with the full amount on 3.6?
>
> On 3.6:
>
> MemTotal: 8060528 kB
> ...
> DirectMap4k: 2048 kB
> DirectMap2M: 7229440 kB
>
> So it's showing significantly less direct mapped than is included
> in MemTotal (which itself omits some areas of reserved memory).
>
> Whereas on 3.4:
>
> MemTotal: 8060760 kB
> ...
> DirectMap4k: 4096 kB
> DirectMap2M: 8275968 kB
>
> Hugh
next prev parent reply other threads:[~2012-10-01 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 10:46 x86_64: wrong DirectMap kB Jamie Gloudon
2012-10-01 15:23 ` Hugh Dickins
2012-10-01 15:43 ` Jamie Gloudon [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-01 8:37 Hugh Dickins
2012-10-02 14:19 ` Jan Beulich
2012-10-02 18:16 ` Hugh Dickins
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=20121001154311.GA2605@darkstar \
--to=jamie.gloudon@gmail.com \
--cc=hughd@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox