From: Hugh Dickins <hughd@google.com>
To: Chris Webb <chris@arachsys.com>
Cc: kvm@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Host where KSM appears to save a negative amount of memory
Date: Sun, 21 Aug 2011 12:29:50 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.00.1108211155300.1252@sister.anvils> (raw)
In-Reply-To: <20110821085614.GA3957@arachsys.com>
On Sun, 21 Aug 2011, Chris Webb wrote:
> We're running KSM on kernel 2.6.39.2 with hosts running a number qemu-kvm
> virtual machines, and it has consistently been saving us a useful amount of
> RAM.
>
> To monitor the effective amount of memory saved, I've been looking at the
> difference between /sys/kernel/mm/ksm/pages_sharing and pages_shared. On a
> typical 32GB host, this has been coming out as at least a hundred thousand
> or so, which is presumably half to one gigabyte worth of 4k pages.
>
> However, this morning we've spotted something odd - a host where
> pages_sharing is smaller than pages_shared, giving a negative saving by the
> above calculation:
>
> # cat /sys/kernel/mm/ksm/pages_sharing
> 1099994
> # cat /sys/kernel/mm/ksm/pages_shared
> 1761313
>
> I think this means my interpretation of these values must be wrong, as I
> presumably can't have more pages being shared than instances of their use!
> Can anyone shed any light on what might be going on here for me? Am I
> misinterpreting these values, or does this look like it might be an
> accounting bug? (If the latter, what useful debug info can I extract from
> the system to help identify it?)
Your interpretation happens to be wrong, it is expected behaviour,
but I agree it's a little odd.
KSM chooses to show the numbers pages_shared and pages_sharing as
exclusive counts: pages_sharing indicates the saving being made. So it
would be perfectly reasonable to add those two numbers together to get
the "total" number of pages sharing, the number you expected it to show;
but it doesn't make sense to subtract shared from sharing.
(I think Documentation/vm/ksm.txt does make that clear.)
But you'd be right to question further, how come pages_sharing is less
than pages_shared: what is a shared page if it's not being shared with
anything else? (And, at the extreme, it might be that all those 1099994
pages_sharing are actually sharing the same one of the pages_shared.)
It's a page that was shared with (at least one) others before, but all
but one of these instances have got freed since, and we've left this
page in the "shared tree", so that it can be more quickly matched up
with duplicates in future when they appear, as seems quite likely.
We don't actively do anything to move them out of the shared state:
some effort was needed to get them there, and no disadvantage in leaving
them like that; but yes, it is misleading to describe them as "shared".
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-21 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 8:56 Chris Webb
2011-08-21 19:29 ` Hugh Dickins [this message]
2011-08-22 7:52 ` Chris Webb
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=alpine.LSU.2.00.1108211155300.1252@sister.anvils \
--to=hughd@google.com \
--cc=chris@arachsys.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.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