On 06/23/2017 09:22 AM, Jan Beulich wrote:
On 23.06.17 at 15:11, wrote:
On 06/23/2017 05:36 AM, Jan Beulich wrote:
On 22.06.17 at 20:57, wrote:
Deferred:
* Per-node heap locks. In addition to (presumably) improving performance in
general, once they are available we can parallelize scru
>>> On 23.06.17 at 15:11, wrote:
> On 06/23/2017 05:36 AM, Jan Beulich wrote:
> On 22.06.17 at 20:57, wrote:
>>> Deferred:
>>> * Per-node heap locks. In addition to (presumably) improving performance in
>>>general, once they are available we can parallelize scrubbing further by
>>>all
On 06/23/2017 05:36 AM, Jan Beulich wrote:
On 22.06.17 at 20:57, wrote:
Deferred:
* Per-node heap locks. In addition to (presumably) improving performance in
general, once they are available we can parallelize scrubbing further by
allowing more than one core per node to do idle loop scr
>>> On 22.06.17 at 20:57, wrote:
> Deferred:
> * Per-node heap locks. In addition to (presumably) improving performance in
> general, once they are available we can parallelize scrubbing further by
> allowing more than one core per node to do idle loop scrubbing.
I don't understand: A per-nod
Changes in v5:
* Make page_info.u.free and union and use bitfields there.
* Bug fixes
(see per-patch notes)
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
