On Tue, Mar 13, 2018 at 04:33:43PM +0800, junyan...@intel.com wrote:
> From: Junyan He
>
> The nvdimm size is huge, sometimes it is more than 256G or even more.
> This is a huge burden for snapshot saving. One snapshot point with
> nvdimm may occupy more than 50G disk space
] RFC: Optimize nvdimm kind memory for
snapshot.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
set -e
git submodule update --init dtc
# Let docker tests dump environment info
export SHOW_ENV=1
export J=8
time make docker-test-mingw@fedora
=== TEST SCRIPT END ===
Updating
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1520930033-18885-1-git-send-email-junyan...@intel.com
Subject: [Qemu-devel] [PATCH 00/10] RFC: Optimize nvdimm kind memory for
snapshot.
=== TEST SCRIPT BEGIN ===
#!/bin
From: Junyan He
The nvdimm size is huge, sometimes it is more than 256G or even more.
This is a huge burden for snapshot saving. One snapshot point with
nvdimm may occupy more than 50G disk space even with compression
enabled.
We need to introduce dependent snapshot manner
/10] RFC: Optimize nvdimm kind memory for
snapshot.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
set -e
git submodule update --init dtc
# Let docker tests dump environment info
export SHOW_ENV=1
export J=8
time make docker-test-mingw@fedora
=== TEST SCRIPT END ===
Updating
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1520990418-28258-1-git-send-email-junyan...@hotmail.com
Subject: [Qemu-devel] [PATCH 00/10] RFC: Optimize nvdimm kind memory for
snapshot.
=== TEST SCRIPT BEGIN ===
#!/bin
From: Junyan He
The nvdimm size is huge, sometimes it is more than 256G or even more.
This is a huge burden for snapshot saving. One snapshot point with
nvdimm may occupy more than 50G disk space even with compression
enabled.
We need to introduce dependent snapshot manner