From: John Allen <jallen@linux.vnet.ibm.com>
To: Nathan Fontenot <nfont@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: sahilmehta17@gmail.com
Subject: Re: [PATCH v6 3/3] powerpc/pseries: Implement indexed-count hotplug memory remove
Date: Thu, 27 Oct 2016 09:22:48 -0500 [thread overview]
Message-ID: <c39e13b4-c7f8-312b-6197-40d710750133@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161018172053.37287.78128.stgit@ltcalpine2-lp14.aus.stglabs.ibm.com>
On 10/18/2016 12:21 PM, Nathan Fontenot wrote:
> From: Sahil Mehta <sahilmehta17@gmail.com>
>
> Indexed-count remove for memory hotplug guarantees that a contiguous block
> of <count> lmbs beginning at a specified <index> will be unassigned (NOT
> that <count> lmbs will be removed). Because of Qemu's per-DIMM memory
> management, the removal of a contiguous block of memory currently
> requires a series of individual calls. Indexed-count remove reduces
> this series into a single call.
>
> Signed-off-by: Sahil Mehta <sahilmehta17@gmail.com>
> Signed-off-by: Nathan Fontenot <nfont@linux.vnet.ibm.com>
> ---
Reviewed-by: John Allen <jallen@linux.vnet.ibm.com>
next prev parent reply other threads:[~2016-10-27 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 17:20 [PATCH v6 0/3] powerpc/pseries: Implement indexed-count memory hotplug Nathan Fontenot
2016-10-18 17:20 ` [PATCH v6 1/3] powerpc/pseries: Correct possible read beyond dlpar sysfs buffer Nathan Fontenot
2016-10-27 14:20 ` John Allen
2016-10-18 17:20 ` [PATCH v6 2/3] powerpc/pseries: Implement indexed-count hotplug memory add Nathan Fontenot
2016-10-27 14:21 ` John Allen
2016-10-18 17:21 ` [PATCH v6 3/3] powerpc/pseries: Implement indexed-count hotplug memory remove Nathan Fontenot
2016-10-27 14:22 ` John Allen [this message]
2016-11-15 0:58 ` Michael Roth
2016-11-15 20:09 ` Nathan Fontenot
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=c39e13b4-c7f8-312b-6197-40d710750133@linux.vnet.ibm.com \
--to=jallen@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=sahilmehta17@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).