From: Michael Heyse <mhk@designassembly.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: which one is broken: VIA padlock aes or aes_i586?
Date: Wed, 22 Feb 2006 12:49:16 +0100 [thread overview]
Message-ID: <43FC4FBC.7030103@designassembly.de> (raw)
In-Reply-To: <20060222013137.GA844@gondor.apana.org.au>
Herbert Xu wrote:
> I don't think this patch is your problem since it's part of the multiblock
> code which doesn't exist in 2.6.12 at all. Of course the multiblock code
> itself could be buggy. I'll take a look.
You're right, this doesn't make sense. I tried it with 2.6.15.4, and it works, 2.6.16-rc1 doesn't. In both cases no other AES algorithm than padlock was compiled into the kernel. I hope this helps.
BTW: 2.6.15 gives me a read performance increase of about 50% (hdparm -t) compared to 2.6.12, nice work!!
Michael
prev parent reply other threads:[~2006-02-22 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 12:27 which one is broken: VIA padlock aes or aes_i586? Michael Heyse
2006-02-22 1:31 ` Herbert Xu
2006-02-22 11:45 ` Herbert Xu
2006-02-22 12:05 ` Michael Heyse
2006-02-22 12:32 ` [SOLVED] " Michael Heyse
2006-02-22 12:43 ` Herbert Xu
2006-02-22 11:49 ` Michael Heyse [this message]
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=43FC4FBC.7030103@designassembly.de \
--to=mhk@designassembly.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.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