From: Denys Vlasenko <vda.linux@googlemail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Noriaki TAKAMIYA <takamiya@linux-ipv6.org>,
davem@davemloft.net, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 1/4] camellia: 64-bit optimization
Date: Thu, 22 Nov 2007 14:29:36 -0800 [thread overview]
Message-ID: <200711221429.36309.vda.linux@googlemail.com> (raw)
In-Reply-To: <20071122122528.GA9556@gondor.apana.org.au>
On Thursday 22 November 2007 04:25, Herbert Xu wrote:
> On Wed, Nov 21, 2007 at 12:23:49AM -0800, Denys Vlasenko wrote:
> > On Wednesday 21 November 2007 00:22, Denys Vlasenko wrote:
> > > Patches start from 5 because pathches 1..4 are already
> > > in cryptodev-2.6.
> > >
> > > camellia5:
> > > adds 64-bit key setup, it is used if BITS_PER_LONG is 64.
> >
> > Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
>
> Denys, I really appreciate your work in cleaning this algorithm up.
>
> However, I just can't accept 600 lines of new code just to do setkey
> faster/smaller on 64-bit platforms. You know, some people have to
> study these files line-by-line in order have them pass government
> certifications and such.
480 lines after all patches are applied.
> OK I went back and looked at the figures, so we're talking about
> either 1K extra on 64-bit if we use the 32-bit version or 2K extra
> on 32-bit if we went for the 64-bit version.
>
> Either way it doesn't seem to be a big deal. So how about just
> picking one and sticking with it?
"No big deal" approach resulted in thish module having 30k of code.
I cut it down to 20-18k.
In aic7xxx driver, similarly, I rediced size from 300k to 200k.
Still not in mainline. This is depressing.
I am an -Os guy and for me 1k out of 20k module doesn't sound too small.
I will rework and repost patches so that 64-bit code is added by last
patch, feel free to not apply it.
--
vda
next prev parent reply other threads:[~2007-11-22 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 8:22 [PATCH 0/4] camellia: 64-bit optimization and code shrink Denys Vlasenko
2007-11-21 8:23 ` [PATCH 1/4] camellia: 64-bit optimization Denys Vlasenko
2007-11-22 12:25 ` Herbert Xu
2007-11-22 22:29 ` Denys Vlasenko [this message]
2007-11-21 8:25 ` [PATCH 2/4] camellia: code shrink Denys Vlasenko
2007-11-22 12:28 ` Herbert Xu
2007-11-21 8:25 ` [PATCH 3/4] camellia: code shrink 2 Denys Vlasenko
2007-11-21 8:32 ` [PATCH 4/4] camellia: code shrink 3 Denys Vlasenko
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=200711221429.36309.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=takamiya@linux-ipv6.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 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.