From: Steffen Klassert <steffen.klassert@secunet.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: cpu_active vs pcrypt & padata
Date: Tue, 20 Mar 2012 08:44:57 +0100 [thread overview]
Message-ID: <20120320074457.GE29891@secunet.com> (raw)
In-Reply-To: <1332018034.18960.247.camel@twins>
On Sat, Mar 17, 2012 at 10:00:34PM +0100, Peter Zijlstra wrote:
> On Fri, 2012-03-16 at 11:44 +0100, Steffen Klassert wrote:
> >
> > pcrypt uses cpu_active to tell padata which cpuset it whishes
> > to use for parallelization. I could try to push the cpumask
> > handling down to padata if you want to limit this to the core
> > kernel.
>
> /me more confused now.. cpu_active isn't in any way shape or form
> related to cpusets.
When looking at this, it seems that cpu_online_mask is the mask
we should use instead of cpu_active_mask. I'll go in for a closer
look at the end of the week.
> >
> > The padata code is generic and not limited to crypto, you can find
> > a documentation at Documentation/padata.txt.
>
> Would be nice to have a short blurb in kernel/padata.c with a reference
> to that Documentation stuff for more in-depth bits.
Indeed, I'll take care for this.
next prev parent reply other threads:[~2012-03-20 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 10:13 cpu_active vs pcrypt & padata Peter Zijlstra
2012-03-16 10:16 ` David Miller
2012-03-16 10:20 ` Peter Zijlstra
2012-03-16 10:32 ` David Miller
2012-03-16 10:42 ` Peter Zijlstra
2012-03-16 10:44 ` Steffen Klassert
2012-03-17 21:00 ` Peter Zijlstra
2012-03-20 7:44 ` Steffen Klassert [this message]
2012-03-16 13:15 ` Jonathan Corbet
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=20120320074457.GE29891@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.