public inbox for virtualization@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Jack Thomson <jackabt.amazon@gmail.com>,
	mst@redhat.com, jasowang@redhat.com
Cc: xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
	virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
	kalyazin@amazon.co.uk, xmarcalx@amazon.co.uk, jackabt@amazon.com
Subject: Re: [RFC PATCH] virtio_balloon: Support wait on ACK for hinting
Date: Mon, 19 Jan 2026 16:50:06 +0100	[thread overview]
Message-ID: <6c3f8061-302e-40c1-829b-2f8555bee70c@kernel.org> (raw)
In-Reply-To: <20260119154236.39412-1-jackabt.amazon@gmail.com>

On 1/19/26 16:42, Jack Thomson wrote:
> From: Jack Thomson <jackabt@amazon.com>
> 
> This RFC patch adds a new virtio feature for the virtio-balloon driver
> during free page hinting, which will wait on device ack before
> committing the range to the free_page_list. The reason for the change is
> it allows the device to modify this range without it being reclaimed
> from the free_page_list before the ack is sent. As expected, testing
> shows this adds overhead to the hinting run duration, increasing it by
> ~30% with our Firecracker setup. Currently free page hinting is used
> mainly for live migration, but this would open it up for a new use-case.
> 
> We would like to leverage this with MADV_DONTNEED to reduce RSS of a
> guest. We'd like to use hinting because of the flexibility of control it
> brings compared to reporting, allowing memory to be reclaimed in
> deterministic periods. 

Can you elaborate in more detail why you don't simply use reporting, 
like QEMU?

Could you instead see optimizations being done to reporting that could 
make it fly for your use case?

Hinting is a rather special case thing only used for reducing VM 
migration time in QEMU AFAIR.

-- 
Cheers

David

  reply	other threads:[~2026-01-19 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 15:42 [RFC PATCH] virtio_balloon: Support wait on ACK for hinting Jack Thomson
2026-01-19 15:50 ` David Hildenbrand (Red Hat) [this message]
2026-01-19 16:30   ` Thomson, Jack
2026-02-11 20:22     ` David Hildenbrand (Arm)

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=6c3f8061-302e-40c1-829b-2f8555bee70c@kernel.org \
    --to=david@kernel.org \
    --cc=eperezma@redhat.com \
    --cc=jackabt.amazon@gmail.com \
    --cc=jackabt@amazon.com \
    --cc=jasowang@redhat.com \
    --cc=kalyazin@amazon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xmarcalx@amazon.co.uk \
    --cc=xuanzhuo@linux.alibaba.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox