From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: padata: Fixes for 3.4
Date: Wed, 28 Mar 2012 08:41:57 +0200 [thread overview]
Message-ID: <20120328064157.GD16191@secunet.com> (raw)
This patchset contains the following changes:
1) Add a reference to the padata api documentation to the code.
Suggested by Peter Zijlstra.
2) We use the active cpumask to determine the superset of cpus
to use for parallelization. The active cpumask is not the appropriate
cpumask for these purposes. Replace the cpu active usage by cpu online.
Reported by Peter Zijlstra.
3) On cpu hotplug, we don't remove the cpu that went offline from our cpumasks.
Fix this by removing this cpu from the padata cpumasks.
Please pull or apply.
The patchset is based on the crypto-2.6 tree and is available via git:
The following changes since commit ff0a70fe053614e763eb3ac88bfea9c5615fce3b:
Jussi Kivilinna (1):
crypto: twofish-x86_64-3way - module init/exit functions should be static
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/klassert/linux-stk padata-fixes
Steffen Klassert (3):
padata: Add a reference to the api documentation
padata: Use the online cpumask as the default
padata: Fix cpu hotplug
kernel/padata.c | 13 +++++++++----
1 files changed, 9 insertions(+), 4 deletions(-)
next reply other threads:[~2012-03-28 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 6:41 Steffen Klassert [this message]
2012-03-28 6:42 ` [PATCH 1/3] padata: Add a reference to the api documentation Steffen Klassert
2012-03-28 6:43 ` [PATCH 2/3] padata: Use the online cpumask as the default Steffen Klassert
2012-03-28 6:44 ` [PATCH 3/3] padata: Fix cpu hotplug Steffen Klassert
2012-03-30 9:20 ` padata: Fixes for 3.4 Herbert Xu
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=20120328064157.GD16191@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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).