On 20.01.2016 14:36, Vladimir Sementsov-Ogievskiy wrote:
On 19.01.2016 11:53, Xiao Guangrong wrote:
On 01/18/2016 07:42 PM, Denis V. Lunev wrote:
From: Vladimir Sementsov-Ogievskiy
NVDIMM for now is planned to use as a backing store for DAX filesystem
in the guest and thus this memory is ex
On 01/20/2016 07:36 PM, Vladimir Sementsov-Ogievskiy wrote:
On 19.01.2016 11:53, Xiao Guangrong wrote:
On 01/18/2016 07:42 PM, Denis V. Lunev wrote:
From: Vladimir Sementsov-Ogievskiy
NVDIMM for now is planned to use as a backing store for DAX filesystem
in the guest and thus this memory
On 19.01.2016 11:53, Xiao Guangrong wrote:
On 01/18/2016 07:42 PM, Denis V. Lunev wrote:
From: Vladimir Sementsov-Ogievskiy
NVDIMM for now is planned to use as a backing store for DAX filesystem
in the guest and thus this memory is excluded from guest memory
management
and LRUs.
In this c
On 01/18/2016 04:42 AM, Denis V. Lunev wrote:
> From: Vladimir Sementsov-Ogievskiy
>
> NVDIMM for now is planned to use as a backing store for DAX filesystem
> in the guest and thus this memory is excluded from guest memory management
> and LRUs.
>
> In this case libvirt running QEMU along with
On 01/18/2016 07:42 PM, Denis V. Lunev wrote:
From: Vladimir Sementsov-Ogievskiy
NVDIMM for now is planned to use as a backing store for DAX filesystem
in the guest and thus this memory is excluded from guest memory management
and LRUs.
In this case libvirt running QEMU along with configured
From: Vladimir Sementsov-Ogievskiy
NVDIMM for now is planned to use as a backing store for DAX filesystem
in the guest and thus this memory is excluded from guest memory management
and LRUs.
In this case libvirt running QEMU along with configured ballon almost
immediately inflates balloon and ef
