From: John Allen <jallen@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, nfont@linux.vnet.ibm.com
Subject: [PATCH v2 0/2] powerpc/pseries: Improve serialization of PRRN events
Date: Tue, 17 Jul 2018 14:40:46 -0500 [thread overview]
Message-ID: <20180717194048.3057-1-jallen@linux.ibm.com> (raw)
Stress testing has uncovered issues with handling continuously queued PRRN
events. Running PRRN events in this way can seriously load the system given
the sheer volume of dlpar being handled. This patchset ensures that PRRN
events are handled more synchronously, only allowing the PRRN handler to
queue a single dlpar event at any given time. Additionally, it ensures
that rtas polling continues normally when multiple PRRN events are queued
simultaneously.
v2:
-Unlock prrn_lock when PRRN operations are complete, not after handler is
scheduled.
-Remove call to flush_work, the previous broken method of serializing
PRRN events.
John Allen (2):
powerpc/pseries: Avoid blocking rtas polling handling multiple PRRN
events
powerpc/pseries: Wait for completion of hotplug events during PRRN
handling
arch/powerpc/kernel/rtasd.c | 10 +++++++---
arch/powerpc/platforms/pseries/mobility.c | 5 ++++-
2 files changed, 11 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2018-07-17 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 19:40 John Allen [this message]
2018-07-17 19:40 ` [PATCH v2 1/2] powerpc/pseries: Avoid blocking rtas polling handling multiple PRRN events John Allen
2018-07-20 16:12 ` Nathan Fontenot
2018-07-23 13:27 ` Michael Ellerman
2018-07-23 15:05 ` John Allen
2018-08-01 13:02 ` Michael Ellerman
2018-08-06 19:09 ` John Allen
2018-07-17 19:40 ` [PATCH v2 2/2] powerpc/pseries: Wait for completion of hotplug events during PRRN handling John Allen
2018-07-20 16:12 ` Nathan Fontenot
2018-07-23 13:41 ` Michael Ellerman
2018-07-23 15:22 ` John Allen
2018-08-01 13:16 ` Michael Ellerman
2018-08-07 19:26 ` John Allen
2018-08-08 13:38 ` Michael Ellerman
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=20180717194048.3057-1-jallen@linux.ibm.com \
--to=jallen@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.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).