qemu-s390x
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v1 07/17] migration/rdma: Use ram_block_discard_set_broken()


From: David Hildenbrand
Subject: Re: [PATCH v1 07/17] migration/rdma: Use ram_block_discard_set_broken()
Date: Fri, 15 May 2020 16:09:39 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0

On 15.05.20 14:45, Dr. David Alan Gilbert wrote:
> * David Hildenbrand (address@hidden) wrote:
>> RDMA will pin all guest memory (as documented in docs/rdma.txt). We want
>> to mark RAM block discards to be broken - however, to keep it simple
>> use ram_block_discard_is_required() instead of inhibiting.
> 
> Should this be dependent on whether rdma->pin_all is set?
> Even with !pin_all some will be pinned at any given time
> (when it's registered with the rdma stack).

Do you know how much memory this is? Is such memory only temporarily pinned?

At least with special-cases of vfio, it's acceptable if some memory is
temporarily pinned - we assume it's only the working set of the driver,
which guests will not inflate as long as they don't want to shoot
themselves in the foot.

This here sounds like the guest does not know the pinned memory is
special, right?

-- 
Thanks,

David / dhildenb




reply via email to

[Prev in Thread] Current Thread [Next in Thread]