mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	Steffen Klassert <steffen.klassert@secunet.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	Daniel Jordan <daniel.m.jordan@oracle.com>
Subject: [PATCH v2 0/5] padata flushing and CPU hotplug fixes
Date: Wed, 28 Aug 2019 18:14:20 -0400	[thread overview]
Message-ID: <20190828221425.22701-1-daniel.m.jordan@oracle.com> (raw)

Hi,
Here are some miscellaneous padata fixes, mostly to do with CPU hotplug.
This time around there's a new hotplug state to make the CPU remove path
cleaner, and the CC list grew a bit.

Daniel

v2:
 - patches 1-3 are new; 4-5 have changed since v1[*]
 - attempted to fix padata flushing as requested (Herbert)
 - changed hotplug state in which __padata_remove_cpu() is
   called (Herbert)
 - purged cpumask_clear_cpu() calls from same function (Herbert)
 - dropped v1's patch 3/2 (Herbert)
 - after more thought, left the Fixes: tag on the last patch the same

testing:
 - testcase was tcrypt mode=215 sec=1 throughout
 - ran all cpumask combos among parallel cpumasks, serial cpumasks, and CPU
   hotplug in a 3-CPU VM
 - lockdep to check patch 4
 - tested at each patch in this set with and without
   CONFIG_CRYPTO_PCRYPT

Series based on recent mainline plus all padata patches in cryptodev:
    git://oss.oracle.com/git/linux-dmjordan.git padata-cpuhp-v2

[*] https://lore.kernel.org/linux-crypto/20190809192857.26585-1-daniel.m.jordan@oracle.com/

Daniel Jordan (5):
  padata: make flushing work with async users
  padata: remove reorder_objects
  padata: get rid of padata_remove_cpu() for real
  padata: always acquire cpu_hotplug_lock before pinst->lock
  padata: validate cpumask without removed CPU during offline

 Documentation/padata.txt   | 18 ++------
 include/linux/cpuhotplug.h |  1 +
 include/linux/padata.h     |  5 +-
 kernel/padata.c            | 95 +++++++++++---------------------------
 4 files changed, 36 insertions(+), 83 deletions(-)


base-commit: d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1
prerequisite-patch-id: a5bfed8ea60d5a784b8b3e21ccb5657ced2aa1e3
prerequisite-patch-id: 96d53aecccb5af242ba5ee342d75810ecd9bfb84
prerequisite-patch-id: 965d8a63c1461f00219aec2d817f2ca85d49cfb3
prerequisite-patch-id: 8e6c2988331b46c9467ac568157c6c575cbe6578
-- 
2.23.0


             reply	other threads:[~2019-08-28 23:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 22:14 Daniel Jordan [this message]
2019-08-28 22:14 ` [PATCH v2 1/5] padata: make flushing work with async users Daniel Jordan
2019-09-05  4:17   ` Herbert Xu
2019-09-05 22:37     ` Daniel Jordan
2019-09-18 20:37       ` Daniel Jordan
2019-08-28 22:14 ` [PATCH v2 2/5] padata: remove reorder_objects Daniel Jordan
2019-08-28 22:14 ` [PATCH v2 3/5] padata: get rid of padata_remove_cpu() for real Daniel Jordan
2019-08-28 22:14 ` [PATCH v2 4/5] padata: always acquire cpu_hotplug_lock before pinst->lock Daniel Jordan
2019-08-28 22:14 ` [PATCH v2 5/5] padata: validate cpumask without removed CPU during offline Daniel Jordan

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=20190828221425.22701-1-daniel.m.jordan@oracle.com \
    --to=daniel.m.jordan@oracle.com \
    --cc=bigeasy@linutronix.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®