From: David Hildenbrand <david@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Nitesh Narayan Lal <nitesh@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, pbonzini@redhat.com, lcapitulino@redhat.com,
pagupta@redhat.com, wei.w.wang@intel.com,
yang.zhang.wz@gmail.com, riel@surriel.com, dodgen@google.com,
konrad.wilk@oracle.com, dhildenb@redhat.com, aarcange@redhat.com,
alexander.duyck@gmail.com
Subject: Re: On guest free page hinting and OOM
Date: Mon, 1 Apr 2019 16:54:49 +0200 [thread overview]
Message-ID: <5c64d235-a17d-b832-5cea-9e2a991823d2@redhat.com> (raw)
In-Reply-To: <20190401104608-mutt-send-email-mst@kernel.org>
On 01.04.19 16:47, Michael S. Tsirkin wrote:
> On Mon, Apr 01, 2019 at 04:11:42PM +0200, David Hildenbrand wrote:
>>> The interesting thing is most probably: Will the hinting size usually be
>>> reasonable small? At least I guess a guest with 4TB of RAM will not
>>> suddenly get a hinting size of hundreds of GB. Most probably also only
>>> something in the range of 1GB. But this is an interesting question to
>>> look into.
>>>
>>> Also, if the admin does not care about performance implications when
>>> already close to hinting, no need to add the additional 1Gb to the ram size.
>>
>> "close to OOM" is what I meant.
>
> Problem is, host admin is the one adding memory. Guest admin is
> the one that knows about performance.
If we think about guest admins only caring about performance, then a
guest admin owill unloads virtio-balloon module to
a) get all the memory available (inflated memory returned to the guest)
b) not use hinting :)
But I get your idea. One side wants hinting, other side has to agree.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-04-01 14:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 13:26 On guest free page hinting and OOM 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 [this message]
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
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=5c64d235-a17d-b832-5cea-9e2a991823d2@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;
as well as URLs for NNTP newsgroup(s).