On 1/9/25 5:18 PM, Peter Xu wrote:
On Thu, Jan 09, 2025 at 11:47:40AM +0300, Daniil Tatianin wrote:
On 12/12/24 7:20 PM, Peter Xu wrote:
On Thu, Dec 12, 2024 at 02:04:33AM +0300, Daniil Tatianin wrote:
Locking the memory without MCL_ONFAULT instantly prefaults any mmaped
anonymous memory wit
On Thu, Jan 09, 2025 at 11:47:40AM +0300, Daniil Tatianin wrote:
> On 12/12/24 7:20 PM, Peter Xu wrote:
>
> > On Thu, Dec 12, 2024 at 02:04:33AM +0300, Daniil Tatianin wrote:
> > > Locking the memory without MCL_ONFAULT instantly prefaults any mmaped
> > > anonymous memory with a write-fault, whic
On 12/12/24 7:20 PM, Peter Xu wrote:
On Thu, Dec 12, 2024 at 02:04:33AM +0300, Daniil Tatianin wrote:
Locking the memory without MCL_ONFAULT instantly prefaults any mmaped
anonymous memory with a write-fault, which introduces a lot of extra
overhead in terms of memory usage when all you want to
On 12.12.24 02:04, Daniil Tatianin wrote:
Locking the memory without MCL_ONFAULT instantly prefaults any mmaped
anonymous memory with a write-fault, which introduces a lot of extra
overhead in terms of memory usage when all you want to do is to prevent
kcompactd from migrating and compacting QEMU
On Thu, Dec 12, 2024 at 02:04:33AM +0300, Daniil Tatianin wrote:
> Locking the memory without MCL_ONFAULT instantly prefaults any mmaped
> anonymous memory with a write-fault, which introduces a lot of extra
> overhead in terms of memory usage when all you want to do is to prevent
> kcompactd from
Locking the memory without MCL_ONFAULT instantly prefaults any mmaped
anonymous memory with a write-fault, which introduces a lot of extra
overhead in terms of memory usage when all you want to do is to prevent
kcompactd from migrating and compacting QEMU pages. Add an option to
only lock pages laz
