On 17.12.2020 00:02, Peter Xu wrote:
On Tue, Dec 15, 2020 at 10:53:13PM +0300, Andrey Gruzdev wrote:
First are series of runs without scan-rate-limiting.patch.
Windows 10:
msecs : count distribution
0 -> 1 : 131913 |**
On Tue, Dec 15, 2020 at 10:53:13PM +0300, Andrey Gruzdev wrote:
> First are series of runs without scan-rate-limiting.patch.
> Windows 10:
>
> msecs : count distribution
> 0 -> 1 : 131913 ||
> 2 -> 3
On 11.12.2020 18:09, Peter Xu wrote:
On Fri, Dec 11, 2020 at 04:13:02PM +0300, Andrey Gruzdev wrote:
I've also made wr-fault resolution latency measurements, for the case when
migration
stream is dumped to a file in cached mode.. Should approximately match saving
to the
file fd directly though
On 11.12.2020 18:09, Peter Xu wrote:
On Fri, Dec 11, 2020 at 04:13:02PM +0300, Andrey Gruzdev wrote:
I've also made wr-fault resolution latency measurements, for the case when
migration
stream is dumped to a file in cached mode.. Should approximately match saving
to the
file fd directly though
On Fri, Dec 11, 2020 at 04:13:02PM +0300, Andrey Gruzdev wrote:
> I've also made wr-fault resolution latency measurements, for the case when
> migration
> stream is dumped to a file in cached mode.. Should approximately match saving
> to the
> file fd directly though I used 'migrate exec:<>' usin
On 09.12.2020 13:08, Andrey Gruzdev wrote:
This patch series is a kind of 'rethinking' of Denis Plotnikov's ideas he's
implemented in his series '[PATCH v0 0/4] migration: add background snapshot'.
Currently the only way to make (external) live VM snapshot is using existing
dirty page logging mi
This patch series is a kind of 'rethinking' of Denis Plotnikov's ideas he's
implemented in his series '[PATCH v0 0/4] migration: add background snapshot'.
Currently the only way to make (external) live VM snapshot is using existing
dirty page logging migration mechanism. The main problem is that i
