Greetings,
the circus is back in town -- another version of the guest page hinting
patches. The patches differ from version 6 only in the kernel version,
they apply against 2.6.29. My short sniff test showed that the code
is still working as expected.
To recap (you can skip this if you read the boiler plate of the last
version of the patches):
The main benefit for guest page hinting vs. the ballooner is that there
is no need for a monitor that keeps track of the memory usage of all the
guests, a complex algorithm that calculates the working set sizes and for
the calls into the guest kernel to control the size of the balloons.
The host just does normal LRU based paging. If the host picks one of the
pages the guest can recreate, the host can throw it away instead of writing
it to the paging device. Simple and elegant.
The main disadvantage is the added complexity that is introduced to the
guests memory management code to do the page state changes and to deal
with discard faults.
Right after booting the page states on my 256 MB z/VM guest looked like
this (r=resident, p=preserved, z=zero, S=stable, U=unused,
P=potentially volatile, V=volatile):
<state>|--tot--|---r---|---p---|---z---|
S | 19719| 19673| 0| 46|
U | 235416| 2734| 0| 232682|
P | 1| 1| 0| 0|
V | 7008| 7008| 0| 0|
tot-> | 262144| 29416| 0| 232728|
about 25% of the pages are in voltile state. After grepping through the
linux source tree this picture changes:
<state>|--tot--|---r---|---p---|---z---|
S | 43784| 43744| 0| 40|
U | 78631| 2397| 0| 76234|
P | 2| 2| 0| 0|
V | 139727| 139727| 0| 0|
tot-> | 262144| 185870| 0| 76274|
about 75% of the pages are now volatile. Depending on the workload you
will get different results.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/virtualization
