Re: [PATCH v1 00/13] Ram blocks with resizable anonymous allocations under POSIX

2020-02-10 Thread David Hildenbrand
>> That should work as expected. Resizing *while* kvm is running is tricky, but >> that‘s not part of this series and a different story :) right now, resizing >> is only valid on reboot/incoming migration. > > Hmm 'when' during an incoming migration; I ask because of userfaultfd > setup for post

Re: [PATCH v1 00/13] Ram blocks with resizable anonymous allocations under POSIX

2020-02-07 Thread Dr. David Alan Gilbert
* David Hildenbrand (da...@redhat.com) wrote: > > > > Am 06.02.2020 um 21:11 schrieb Dr. David Alan Gilbert : > > > > * David Hildenbrand (da...@redhat.com) wrote: > >> We already allow resizable ram blocks for anonymous memory, however, they > >> are not actually resized. All memory is mmaped(

Re: [PATCH v1 00/13] Ram blocks with resizable anonymous allocations under POSIX

2020-02-06 Thread David Hildenbrand
> Am 06.02.2020 um 21:11 schrieb Dr. David Alan Gilbert : > > * David Hildenbrand (da...@redhat.com) wrote: >> We already allow resizable ram blocks for anonymous memory, however, they >> are not actually resized. All memory is mmaped() R/W, including the memory >> exceeding the used_length, u

Re: [PATCH v1 00/13] Ram blocks with resizable anonymous allocations under POSIX

2020-02-06 Thread Dr. David Alan Gilbert
* David Hildenbrand (da...@redhat.com) wrote: > We already allow resizable ram blocks for anonymous memory, however, they > are not actually resized. All memory is mmaped() R/W, including the memory > exceeding the used_length, up to the max_length. > > When resizing, effectively only the boundary

Re: [PATCH v1 00/13] Ram blocks with resizable anonymous allocations under POSIX

2020-02-06 Thread David Hildenbrand
On 06.02.20 10:27, Michael S. Tsirkin wrote: > On Mon, Feb 03, 2020 at 07:31:12PM +0100, David Hildenbrand wrote: >> We already allow resizable ram blocks for anonymous memory, however, they >> are not actually resized. All memory is mmaped() R/W, including the memory >> exceeding the used_length,

Re: [PATCH v1 00/13] Ram blocks with resizable anonymous allocations under POSIX

2020-02-06 Thread Michael S. Tsirkin
On Mon, Feb 03, 2020 at 07:31:12PM +0100, David Hildenbrand wrote: > We already allow resizable ram blocks for anonymous memory, however, they > are not actually resized. All memory is mmaped() R/W, including the memory > exceeding the used_length, up to the max_length. > > When resizing, effectiv

[PATCH v1 00/13] Ram blocks with resizable anonymous allocations under POSIX

2020-02-03 Thread David Hildenbrand
We already allow resizable ram blocks for anonymous memory, however, they are not actually resized. All memory is mmaped() R/W, including the memory exceeding the used_length, up to the max_length. When resizing, effectively only the boundary is moved. Implement actually resizable anonymous alloca