Re: [PATCH 0/2] overcommit: introduce mem-lock-onfault

2024-12-10 Thread Daniil Tatianin
On 12/10/24 8:20 PM, Peter Xu wrote: On Tue, Dec 10, 2024 at 08:01:08PM +0300, Daniil Tatianin wrote: I mentioned my use case in the cover letter. Basically we want to protect QEMU's pages from being migrated and compacted by kcompactd, which it accomplishes by modifying live page tables and s

Re: [PATCH 0/2] overcommit: introduce mem-lock-onfault

2024-12-10 Thread Peter Xu
On Tue, Dec 10, 2024 at 08:01:08PM +0300, Daniil Tatianin wrote: > I mentioned my use case in the cover letter. Basically we want to protect > QEMU's pages from being migrated and compacted by kcompactd, which it > accomplishes by modifying live page tables and spamming the process with TLB > inval

Re: [PATCH 0/2] overcommit: introduce mem-lock-onfault

2024-12-10 Thread Daniil Tatianin
On 12/10/24 7:48 PM, Peter Xu wrote: On Mon, Dec 09, 2024 at 10:40:51AM +0300, Daniil Tatianin wrote: On 12/6/24 4:08 AM, Peter Xu wrote: On Fri, Dec 06, 2024 at 02:19:06AM +0300, Daniil Tatianin wrote: Currently, passing mem-lock=on to QEMU causes memory usage to grow by huge amounts: no m

Re: [PATCH 0/2] overcommit: introduce mem-lock-onfault

2024-12-10 Thread Peter Xu
On Mon, Dec 09, 2024 at 10:40:51AM +0300, Daniil Tatianin wrote: > On 12/6/24 4:08 AM, Peter Xu wrote: > > > On Fri, Dec 06, 2024 at 02:19:06AM +0300, Daniil Tatianin wrote: > > > Currently, passing mem-lock=on to QEMU causes memory usage to grow by > > > huge amounts: > > > > > > no memlock: > >

Re: [PATCH 0/2] overcommit: introduce mem-lock-onfault

2024-12-10 Thread Vladimir Sementsov-Ogievskiy
Reviewed-by: Vladimir Sementsov-Ogievskiy -- Best regards, Vladimir

Re: [PATCH 0/2] overcommit: introduce mem-lock-onfault

2024-12-08 Thread Daniil Tatianin
On 12/6/24 4:08 AM, Peter Xu wrote: On Fri, Dec 06, 2024 at 02:19:06AM +0300, Daniil Tatianin wrote: Currently, passing mem-lock=on to QEMU causes memory usage to grow by huge amounts: no memlock: $ qemu-system-x86_64 -overcommit mem-lock=off $ ps -p $(pidof ./qemu-system-x86_64) -o

Re: [PATCH 0/2] overcommit: introduce mem-lock-onfault

2024-12-05 Thread Peter Xu
On Fri, Dec 06, 2024 at 02:19:06AM +0300, Daniil Tatianin wrote: > Currently, passing mem-lock=on to QEMU causes memory usage to grow by > huge amounts: > > no memlock: > $ qemu-system-x86_64 -overcommit mem-lock=off > $ ps -p $(pidof ./qemu-system-x86_64) -o rss= > 45652 > > $ ./

[PATCH 0/2] overcommit: introduce mem-lock-onfault

2024-12-05 Thread Daniil Tatianin
Currently, passing mem-lock=on to QEMU causes memory usage to grow by huge amounts: no memlock: $ qemu-system-x86_64 -overcommit mem-lock=off $ ps -p $(pidof ./qemu-system-x86_64) -o rss= 45652 $ ./qemu-system-x86_64 -overcommit mem-lock=off -enable-kvm $ ps -p $(pidof ./qemu-