On 03/01/2017 11:27 AM, Jan Beulich wrote:
On 01.03.17 at 17:14, wrote:
>> On 03/01/2017 10:48 AM, George Dunlap wrote:
>>> On 27/02/17 17:06, Boris Ostrovsky wrote:
Since dirty pages are always at the tail of page lists we are not really
searching the lists. As soon as a clean page
>>> On 01.03.17 at 17:14, wrote:
> On 03/01/2017 10:48 AM, George Dunlap wrote:
>> On 27/02/17 17:06, Boris Ostrovsky wrote:
>>> Since dirty pages are always at the tail of page lists we are not really
>>> searching the lists. As soon as a clean page is found (starting from the
>>> tail) we can st
On 03/01/2017 10:48 AM, George Dunlap wrote:
> On 27/02/17 17:06, Boris Ostrovsky wrote:
Briefly, the new algorithm places dirty pages at the end of heap's page
list
for each node/zone/order to avoid having to scan full list while searching
for dirty pages. One processor form e
On 27/02/17 17:06, Boris Ostrovsky wrote:
>>> Briefly, the new algorithm places dirty pages at the end of heap's page list
>>> for each node/zone/order to avoid having to scan full list while searching
>>> for dirty pages. One processor form each node checks whether the node has
>>> any
>>> dirty
On 27/02/17 17:06, Boris Ostrovsky wrote:
>>> This series adds support for scrubbing released pages from idle loop,
>>> making guest destruction significantly faster. For example, destroying a
>>> 1TB guest can now be completed in slightly over 1 minute as opposed to
>>> about 9 minutes using exist
>> This series adds support for scrubbing released pages from idle loop,
>> making guest destruction significantly faster. For example, destroying a
>> 1TB guest can now be completed in slightly over 1 minute as opposed to
>> about 9 minutes using existing scrubbing algorithm.
> What is this 1m no
On 27/02/17 00:37, Boris Ostrovsky wrote:
> (Resending with corrected Tim's address, sorry)
>
> When a domain is destroyed the hypervisor must scrub domain's pages before
> giving them to another guest in order to prevent leaking the deceased
> guest's data. Currently this is done during guest's de
(Resending with corrected Tim's address, sorry)
When a domain is destroyed the hypervisor must scrub domain's pages before
giving them to another guest in order to prevent leaking the deceased
guest's data. Currently this is done during guest's destruction, possibly
causing very lengthy cleanup pr
