On Mon, Dec 12, 2011 at 05:10:45PM -0600, Bob Pearson wrote:
> That choice was for Joakim who measured better performance on his 32 bit PPC
> platform with "by 4".
Ok. On my 1.33GHz PowerBook I get ~255MB/s with slice by 4 and ~270MB/s with
slice by 8. I think it's a PPC 7447, and definitely 32-
On Tue, 2011-12-13 at 00:06 +0100, roel wrote:
> The test not [val1] or not [val2] always evaluates to true
Hello
Looking at drivers with:
$ grep -rP --include=*.[ch]
"(\b[\w\[\]\>\._\-]+)\s*\!\=\s*[\w\[\]\>\._\-]+\s*\|\|\s*\1\s*\!\=" drivers
drivers/media/video/s5p-fimc/fimc-capture.c:
On Tue, 2011-12-13 at 00:06 +0100, roel wrote:
> The test not [val1] or not [val2] always evaluates to true
Hey Jamie and Roel
Looking at drivers with:
$ grep -rP --include=*.[ch]
"(\b[\w\[\]\>\._\-]+)\s*\!\=\s*[\w\[\]\>\._\-]+\s*\|\|\s*\1\s*\!\=" drivers
drivers/crypto/picoxcell_crypto.c:
That choice was for Joakim who measured better performance on his 32 bit PPC
platform with "by 4".
> -Original Message-
> From: Darrick J. Wong [mailto:djw...@us.ibm.com]
> Sent: Monday, December 12, 2011 4:59 PM
> To: Herbert Xu; Bob Pearson
> Cc: Andrew Morton; Theodore Tso; Joakim Tjern
On Fri, Dec 02, 2011 at 06:36:46PM -0800, Darrick J. Wong wrote:
> On Fri, Dec 02, 2011 at 08:25:05AM +0800, Herbert Xu wrote:
> > On Thu, Dec 01, 2011 at 12:15:17PM -0800, Darrick J. Wong wrote:
> > > Allow the kernel builder to choose a crc32* algorithm for the kernel.
> > >
> > > Signed-off-by:
manual removal of double-spaces - no non-whitespace changes.
Signed-off-by: Kim Phillips
---
drivers/crypto/caam/desc.h | 335 ++--
1 files changed, 167 insertions(+), 168 deletions(-)
diff --git a/drivers/crypto/caam/desc.h b/drivers/crypto/caam/desc.h
As prescribed by Linus:
https://lkml.org/lkml/2011/12/2/290
Signed-off-by: Kim Phillips
---
drivers/crypto/talitos.c | 18 +-
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/crypto/talitos.c b/drivers/crypto/talitos.c
index d376cc7..503d0d8 100644
--- a/
the polarity of the definition for error propagation was reverse
in the initial desc.h. Fix desc.h and its users.
Signed-off-by: Kim Phillips
---
drivers/crypto/caam/caamalg.c | 10 +-
drivers/crypto/caam/desc.h|4 ++--
drivers/crypto/caam/desc_constr.h |7 ---
The first patch in the series fixes a boottime oops on SEC h/w v.2.0.
The rest are minor cleanups.
The fourth - "crypto: caam - desc.h - convert spaces to tabs" -
is the result of running unexpand -a on desc.h, and may exceed list
message quota limits. If this is the case, please execute unexpand
SEC2/3 h/w doesn't have a dedicated interrupt for errors,
and the only callsite for talitos_error has already done
the type conversion, so simplify talitos_error to take a
pointer to a struct device.
Signed-off-by: Kim Phillips
---
drivers/crypto/talitos.c |5 ++---
1 files changed, 2 insert
Access to the SEC4 DECOs (DEscriptor COntrollers) (for debug purposes)
isn't supported or used, and its register access initialization code
erroneously makes illegal i/o accesses that show up as errors when
run under simulation. Remove it until proper support (via DECORR)
is added.
Signed-off-by:
Fix a kfree to an invalid address which causes an oops when running
on SEC v2.0 h/w (introduced in commit 702331b "crypto: talitos - add
hmac algorithms").
Signed-off-by: Kim Phillips
---
drivers/crypto/talitos.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/dri
On Sun, 11 Dec 2011 13:26:26 +0100
Nikos Mavrogiannopoulos wrote:
> The added CRYPTO_ALG_KERN_DRIVER_ONLY flag indicates whether a cipher
> is only available via a kernel driver. If the cipher implementation
> might be available by using an instruction set or by porting the
> kernel code, then it
Rusty Russell wrote:
> OK, then you need to generate stripped modules as part of the build,
> too. It's a bit of a pain, sure, but hardly a showstopper.
They'd have to be maximally stripped so that mkinitrd doesn't do anything to
them, but you'd then get the debuginfo from them into the packagi
On Mon, 12 Dec 2011 01:21:40 +, David Howells wrote:
> Rusty Russell wrote:
>
> > I think you misunderstand, I'm talking about the modinfo command, not
> > the .modinfo section.
>
> Sorry, yes. But why do you need to enhance modinfo?
I was suggesting that you want it to print the signatur
15 matches
Mail list logo