From: David Hildenbrand <david@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Alexander Duyck <alexander.duyck@gmail.com>
Cc: Nitesh Narayan Lal <nitesh@redhat.com>,
kvm list <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Paolo Bonzini <pbonzini@redhat.com>,
lcapitulino@redhat.com, pagupta@redhat.com, wei.w.wang@intel.com,
Yang Zhang <yang.zhang.wz@gmail.com>,
Rik van Riel <riel@surriel.com>,
dodgen@google.com, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
dhildenb@redhat.com, Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: On guest free page hinting and OOM
Date: Tue, 2 Apr 2019 17:57:06 +0200 [thread overview]
Message-ID: <3dd76ce6-c138-b019-3a43-0bb0b793690a@redhat.com> (raw)
In-Reply-To: <20190402112115-mutt-send-email-mst@kernel.org>
On 02.04.19 17:25, Michael S. Tsirkin wrote:
> On Tue, Apr 02, 2019 at 08:04:00AM -0700, Alexander Duyck wrote:
>> Basically what we would be doing is providing a means for
>> incrementally transitioning the buddy memory into the idle/offline
>> state to reduce guest memory overhead. It would require one function
>> that would walk the free page lists and pluck out pages that don't
>> have the "Offline" page type set,
>
> I think we will need an interface that gets
> an offline page and returns the next online free page.
>
> If we restart the list walk each time we can't guarantee progress.
Yes, and essentially we are scanning all the time for chunks vs. we get
notified which chunks are possible hinting candidates. Totally different
design.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-04-02 15:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 13:26 Michael S. Tsirkin
2019-03-29 14:24 ` David Hildenbrand
2019-03-29 15:08 ` Michael S. Tsirkin
2019-03-29 15:37 ` David Hildenbrand
2019-03-29 15:45 ` David Hildenbrand
2019-03-29 16:51 ` Michael S. Tsirkin
2019-04-01 8:17 ` David Hildenbrand
2019-04-01 13:24 ` Michael S. Tsirkin
2019-04-01 14:09 ` David Hildenbrand
2019-04-01 14:11 ` David Hildenbrand
2019-04-01 14:47 ` Michael S. Tsirkin
2019-04-01 14:54 ` David Hildenbrand
2019-04-01 20:56 ` Alexander Duyck
2019-04-02 7:42 ` David Hildenbrand
2019-04-02 15:04 ` Alexander Duyck
2019-04-02 15:25 ` Michael S. Tsirkin
2019-04-02 15:57 ` David Hildenbrand [this message]
2019-04-02 16:18 ` Alexander Duyck
2019-04-02 17:08 ` David Hildenbrand
2019-04-02 17:45 ` Alexander Duyck
2019-04-02 17:53 ` Michael S. Tsirkin
2019-04-02 20:32 ` Alexander Duyck
2019-04-02 18:21 ` David Hildenbrand
2019-04-02 19:49 ` Michael S. Tsirkin
2019-04-02 20:32 ` David Hildenbrand
2019-04-02 15:55 ` David Hildenbrand
2019-04-02 17:30 ` Alexander Duyck
2019-04-02 18:53 ` David Hildenbrand
2019-04-02 23:43 ` Alexander Duyck
2019-04-03 19:43 ` David Hildenbrand
2019-04-04 13:28 ` Michael S. Tsirkin
2019-04-02 16:19 ` David Hildenbrand
2019-04-01 14:45 ` Michael S. Tsirkin
2019-03-29 16:09 ` Michael S. Tsirkin
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=3dd76ce6-c138-b019-3a43-0bb0b793690a@redhat.com \
--to=david@redhat.com \
--cc=aarcange@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=dhildenb@redhat.com \
--cc=dodgen@google.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.com \
--cc=nitesh@redhat.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=riel@surriel.com \
--cc=wei.w.wang@intel.com \
--cc=yang.zhang.wz@gmail.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