From: Andi Kleen <andi@firstfloor.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Andi Kleen" <andi@firstfloor.org>,
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH] [CRYPTO] cast6: inline bloat--
Date: Thu, 10 Jan 2008 10:44:12 +0100 [thread overview]
Message-ID: <20080110094412.GA25292@one.firstfloor.org> (raw)
In-Reply-To: <20080110092746.GA11613@gondor.apana.org.au>
On Thu, Jan 10, 2008 at 08:27:46PM +1100, Herbert Xu wrote:
> On Thu, Jan 10, 2008 at 10:25:55AM +0100, Andi Kleen wrote:
> >
> > Then I don't think the patch should have been applied.
>
> I disagree. There isn't any evidence showing that the inlined version
> is significantly faster either. In the absence of that, the version
> with the smaller size is preferable.
Just seems very risky to mess with cipher inner loops like that. Normally
people originally spent quite some effort tuning those; especially for
an AES candidate. Also putting quite a lot of function calls in there
doesn't seem right -- especially if frame pointer is enabled function
calls are not that cheap anymore. Also it messes up the register
allocation.
> Of course if anyone is keen enough about cast6 to provide benchmarks
If nobody is keen enough then the code could be just dropped
completely, couldn't it?
> showing that the inlined version is significantly faster then I'm
> happy to revert the patch.
There used to be papers with performance analysis of all the AES
candidates, but I cannot find them right now for CAST6. But I doubt
the code was written without proper thought.
-Andi
next prev parent reply other threads:[~2008-01-10 9:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 13:40 [PATCH] [CRYPTO] cast6: inline bloat-- Ilpo Järvinen
2008-01-08 6:33 ` Herbert Xu
2008-01-10 3:03 ` Andi Kleen
2008-01-10 9:17 ` Ilpo Järvinen
2008-01-10 9:25 ` Andi Kleen
2008-01-10 9:27 ` Herbert Xu
2008-01-10 9:44 ` Andi Kleen [this message]
2008-01-10 13:35 ` Sebastian Siewior
2008-01-10 15:46 ` Andi Kleen
2008-01-12 0:09 ` Sebastian Siewior
2008-01-12 0:57 ` Herbert Xu
2008-01-12 8:04 ` Sebastian Siewior
2008-01-12 2:47 ` Andi Kleen
2008-01-12 2:56 ` 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=20080110094412.GA25292@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=herbert@gondor.apana.org.au \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-crypto@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