qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: sparsh mittal <sparsh0mittal@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu & kernel :address generated are non-uniform
Date: Mon, 21 Nov 2011 09:13:45 +0700	[thread overview]
Message-ID: <CAGdaadZrThn1v369Kzovpk1MFZU_RpO30jZuz013Ne-w=0eO2A@mail.gmail.com> (raw)
In-Reply-To: <CAF9M4Zg=_dkiou3AsuwOY6b4Np4Rsh9WbYAmkpBhMeCWdzhdUA@mail.gmail.com>

On Fri, Nov 18, 2011 at 21:49, sparsh mittal <sparsh0mittal@gmail.com> wrote:
> GBrange numberOfAddresses
>
> 0-0.5---> 3325
>
> 0.5-1---> 1253
>
> 1-1.5---> 0
>
> 1.5-2---> 30
>
> 2-2.5---> 0
>
> 2.5-3---> 1708
>
> 3-3.5---> 10521
>
> 3.5-4---> 0
>
> 4-4.5--> 15428

Hi...

I never observe the above address usage like you did, but I think that
is expected.

The reason is that Linux kernel tends to allocate from high memory
(above 896 MiB ) to allocate pages, including their page tables. This
is done to lower the "pressure" against normal memory zone.

Now for the "unbalance" case, I guess that's due the high usage of
slab. I am not sure where in fact they are started to be placed in
RAM. One thing for sure is that they act as cache for frequest used
objects such task structs, bio, socket buffers.

So, as you can take a guess. It's a mechanism in Linux memory
management which is quite complicated. Not sure if there's shortcut to
shape this up.

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

  reply	other threads:[~2011-11-21  2:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 14:49 [Qemu-devel] qemu & kernel :address generated are non-uniform sparsh mittal
2011-11-21  2:13 ` Mulyadi Santosa [this message]
2011-11-21 23:00   ` sparsh mittal

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='CAGdaadZrThn1v369Kzovpk1MFZU_RpO30jZuz013Ne-w=0eO2A@mail.gmail.com' \
    --to=mulyadi.santosa@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sparsh0mittal@gmail.com \
    /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).