All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>, Wei Liu <wei.liu2@citrix.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	David Vrabel <david.vrabel@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: Xen balloon driver improvement (version 1)
Date: Thu, 23 Oct 2014 12:42:03 +0100	[thread overview]
Message-ID: <5448E98B.5020207@citrix.com> (raw)
In-Reply-To: <1414062040.19198.38.camel@citrix.com>

On 23/10/14 12:00, Ian Campbell wrote:
> On Wed, 2014-10-22 at 19:29 +0100, Wei Liu wrote:
>
>>>> For instance, balloon driver can maintain three queues:
>>>>
>>>> 1. queue for 2 MB pages
>>>> 1. queue for 4 KB pages (delegated to core balloon driver)
>>>> 1. queue for pages used to mapped pages from other domain
>>> What about 1GB pages?
>>>
>> I wouldn't bother with 1GB pages here.
> Guests which don't have special privileges are limited to 2M contiguous
> allocations anyway, to stop them from consuming "precious" higher order
> mappings.
>
> I'm not sure that's still worthwhile (e.g. is it valid on ARM or
> shadow/HAP x86? I'm not sure).
>
>> It would require too much work to coalesce 4KB pages to 1GB pages. 
> FWIW in practice You'd probably coalesce 4K pages into 2M  and then 2M
> into 1G.
>
>

Wouldn't it be wonderful to be able to run a 1GB PVH guest on a 1GB HAP
mapping, with the PVH guest making use of 2MB mapping where possible.

PVH (ought) to be able to do away with the MTRR caching issues, the
legacy IO regions, and so long as the guest doesn't balloon pages out or
map a foreign grant, it won't shatter the host superpage.

But in principle, I agree that making better use of 2MB pages is more
important than considering 1GB pages at the moment.

~Andrew

  parent reply	other threads:[~2014-10-23 11:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 16:29 Xen balloon driver improvement (version 1) Wei Liu
2014-10-22 17:32 ` Andrew Cooper
2014-10-22 18:29   ` Wei Liu
2014-10-23 11:00     ` Ian Campbell
2014-10-23 11:05       ` Wei Liu
2014-10-23 11:42       ` Andrew Cooper [this message]
2014-10-23 11:44         ` David Vrabel
2014-10-23 10:09 ` David Vrabel
2014-10-23 10:52   ` Stefano Stabellini
2014-10-23 10:58     ` David Vrabel
2014-10-23 11:04   ` Wei Liu
2014-10-27 11:29   ` Wei Liu
2014-10-23 11:59 ` Ian Campbell
2014-10-23 12:17   ` Wei Liu
2014-10-23 12:27     ` Ian Campbell
2014-10-23 13:00       ` Wei Liu
2014-10-23 14:29         ` Ian Campbell
2014-10-23 14:30 ` Roger Pau Monné
2014-10-23 15:23   ` Wei Liu
2014-10-23 15:57     ` Roger Pau Monné
2014-10-23 16:04       ` Ian Campbell
2014-10-23 16:12         ` Wei Liu
2014-10-24 13:54 ` Dario Faggioli
2014-10-24 14:04   ` Wei Liu

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=5448E98B.5020207@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.