From: Peter Zijlstra <peterz@infradead.org>
To: David Miller <davem@davemloft.net>
Cc: steffen.klassert@secunet.com, mingo@elte.hu, tglx@linutronix.de,
linux-kernel@vger.kernel.org,
Chris Mason <chris.mason@oracle.com>
Subject: Re: cpu_active vs pcrypt & padata
Date: Fri, 16 Mar 2012 11:42:34 +0100 [thread overview]
Message-ID: <1331894554.18960.234.camel@twins> (raw)
In-Reply-To: <20120316.033204.2200537098677808280.davem@davemloft.net>
On Fri, 2012-03-16 at 03:32 -0700, David Miller wrote:
> Beats me, but just because there's only one user doesn't mean it belongs
> tucked away in that one user's subsystem.
Sure, but I was mostly wondering wth it was, the file doesn't really
explain itself.
Also, most times when introducing generic functionality people try to
collect all interested parties and make something that works for
everybody.
I know for a fact that btrfs does the fan out and regroup thing for
block checksumming etc.. Does Chris even know it exists? If he does why
isn't brtfs using it? If its unsuitable, why wasn't it fixed.
I'm not saying its crap or anything -- I haven't looked at it at all,
beyond my grep for cpu_active -- I'm just wondering, and so far it looks
like there's something weird.
next prev parent reply other threads:[~2012-03-16 10:42 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 [this message]
2012-03-16 10:44 ` Steffen Klassert
2012-03-17 21:00 ` Peter Zijlstra
2012-03-20 7:44 ` Steffen Klassert
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=1331894554.18960.234.camel@twins \
--to=peterz@infradead.org \
--cc=chris.mason@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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