linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>,
	paulus@samba.org, benh@kernel.crashing.org,
	bharata@linux.vnet.ibm.com
Cc: lvivier@redhat.com, thuth@redhat.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC 0/3] Prototype PAPR hash page table resizing (guest side)
Date: Thu, 24 Dec 2015 14:52:53 +0530	[thread overview]
Message-ID: <567BB96D.6050504@linux.vnet.ibm.com> (raw)
In-Reply-To: <1450761298-12172-1-git-send-email-david@gibson.dropbear.id.au>

On 12/22/2015 10:44 AM, David Gibson wrote:
> I've discussed with Paul and Ben previously the possibility of
> extending PAPR to allow changing the size of a running guest's hash
> page table (HPT).  This would allow for much more flexible memory
> hotplug, since the HPT wouldn't have to be sized in advance for the
> maximum possible memory size of the guest.

Does it include reducing the size of HPT as well ?

  parent reply	other threads:[~2015-12-24  9:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22  5:14 [RFC 0/3] Prototype PAPR hash page table resizing (guest side) David Gibson
2015-12-22  5:14 ` [RFC 1/3] pseries: Add hypercall wrappers for hash page table resizing David Gibson
2015-12-22  5:14 ` [RFC 2/3] pseries: Add support for hash " David Gibson
2015-12-22  5:14 ` [RFC 3/3] pseries: sysfs hack to trigger a hash page table resize David Gibson
2015-12-22 11:19   ` Denis Kirjanov
2015-12-23  8:45     ` David Gibson
2015-12-23 12:16       ` Denis Kirjanov
2015-12-24  6:37         ` David Gibson
2015-12-24  9:22 ` Anshuman Khandual [this message]
2015-12-24 10:38   ` [RFC 0/3] Prototype PAPR hash page table resizing (guest side) David Gibson
2015-12-28  4:39     ` Anshuman Khandual
2015-12-29  4:09       ` David Gibson

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=567BB96D.6050504@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lvivier@redhat.com \
    --cc=paulus@samba.org \
    --cc=thuth@redhat.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).