From: Sahil Mehta <smehta@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/2] powerpc/pseries: Implemented indexed-count hotplug memory management
Date: Thu, 30 Jun 2016 14:21:05 -0500 [thread overview]
Message-ID: <19ab11fc-9771-1ad4-95d7-d26dd8f18184@linux.vnet.ibm.com> (raw)
Indexed-count memory management allows addition and removal of contiguous
lmb blocks to be added and removed with a single command. When compared
to the series of calls previously required to manage contiguous blocks,
indexed-count decreases command frequency and complexity, consequently
preventing buffer overflow.
-Sahil Mehta
---
include/asm/rtas.h | 2
platforms/pseries/dlpar.c | 32 +++++-
platforms/pseries/hotplug-memory.c | 194 ++++++++++++++++++++++++++++++++++---
3 files changed, 210 insertions(+), 18 deletions(-)
next reply other threads:[~2016-06-30 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 19:21 Sahil Mehta [this message]
2016-06-30 19:22 ` [PATCH 1/2] powerpc/pseries: Implemented indexed-count hotplug memory add Sahil Mehta
2016-07-11 14:31 ` Nathan Fontenot
2016-07-11 16:24 ` Tyrel Datwyler
2016-06-30 19:24 ` [PATCH 2/2] powerpc/pseries: Implemented indexed-count hotplug memory remove Sahil Mehta
2016-07-11 14:36 ` 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=19ab11fc-9771-1ad4-95d7-d26dd8f18184@linux.vnet.ibm.com \
--to=smehta@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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 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).