diff options
author | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | 2013-04-12 12:43:53 -0400 |
---|---|---|
committer | Ian Jackson <Ian.Jackson@eu.citrix.com> | 2013-04-16 16:21:50 +0100 |
commit | 65a11256f294882d6bd1af4af51e42dbbead650d (patch) | |
tree | d70f7467d876de6b3adb7691fe1fe474d70d2c16 /tools/libxc | |
parent | eb42f98a20fd0315e9b50ffbaca822aef46214ab (diff) | |
download | xen-65a11256f294882d6bd1af4af51e42dbbead650d.tar.gz xen-65a11256f294882d6bd1af4af51e42dbbead650d.tar.bz2 xen-65a11256f294882d6bd1af4af51e42dbbead650d.zip |
xl: Fix 'free_memory' to include outstanding_claims value.
Updating to make it clear that free_memory reported by 'xl info'
is influenced by the outstanding claim value. That is the free
memory that will be available to the host once all outstanding
claims have been completed. This modifies the behavior that the
patch titled "xl: 'xl info' print outstanding claims if enabled
(claim_mode=1 in xl.conf)" had - which reported the
outstanding claims and nothing else.
The free_pages as reported by the hypervisor is the currently
available count of pages on the heap. The outstanding pages is
the total amount of pages reserved for guests (so not taken from
the heap yet). As guests are being populated the memory from the
heap shrinks and the outstanding count of pages decreases.
The total memory used for guests increases.
As the available count of pages on the heap and outstanding
claims are intertwined, report the amount of free memory available
to be a combination of that. That is free heap memory minus the
outstanding pages.
We also make some odd choices in reporting. By default we will
only display 'outstanding_claims' if the claim_mode is enabled
in the global configuration file. However, if there are outstanding
claims, we will ignore the claim_mode and report these values.
Suggested-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'tools/libxc')
0 files changed, 0 insertions, 0 deletions