From: Peter Xu <peterx@redhat.com>
To: "Daniil Tatianin" <d-tatianin@yandex-team.ru>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Stefan Weil <sw@weilnetz.de>,
Fabiano Rosas <farosas@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3 4/4] overcommit: introduce mem-lock=on-fault
Date: Thu, 9 Jan 2025 09:18:08 -0500 [thread overview]
Message-ID: <Z3_aoLOjzQ8M0h81@x1n> (raw)
In-Reply-To: <b5ec2f53-4a03-499b-be17-49729a6efca9@yandex-team.ru>
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, 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 lazily as they're faulted by the process by using
> > > MCL_ONFAULT if asked.
> > >
> > > Signed-off-by: Daniil Tatianin <d-tatianin@yandex-team.ru>
> > Reviewed-by: Peter Xu <peterx@redhat.com>
>
> Hi there! This series has 2 reviewed-bys, is there any way you could queue
> it?
I think this part belongs to mainloop/posix.. so maybe Paolo?
Also copied Phil and Peter Maydell.
--
Peter Xu
next prev parent reply other threads:[~2025-01-09 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 23:04 [PATCH v3 0/4] overcommit: introduce mem-lock-onfault Daniil Tatianin
2024-12-11 23:04 ` [PATCH v3 1/4] os: add an ability to lock memory on_fault Daniil Tatianin
2024-12-11 23:04 ` [PATCH v3 2/4] system/vl: extract overcommit option parsing into a helper Daniil Tatianin
2024-12-12 14:44 ` Vladimir Sementsov-Ogievskiy
2024-12-12 16:17 ` Peter Xu
2024-12-11 23:04 ` [PATCH v3 3/4] sysemu: introduce a new MlockState enum Daniil Tatianin
2024-12-12 16:19 ` Peter Xu
2024-12-12 16:56 ` Vladimir Sementsov-Ogievskiy
2024-12-11 23:04 ` [PATCH v3 4/4] overcommit: introduce mem-lock=on-fault Daniil Tatianin
2024-12-12 16:20 ` Peter Xu
2025-01-09 8:47 ` Daniil Tatianin
2025-01-09 14:18 ` Peter Xu [this message]
2025-01-21 11:40 ` Daniil Tatianin
2024-12-12 17:01 ` Vladimir Sementsov-Ogievskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z3_aoLOjzQ8M0h81@x1n \
--to=peterx@redhat.com \
--cc=d-tatianin@yandex-team.ru \
--cc=farosas@suse.de \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.