All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Vlasenko <vda.linux@googlemail.com>
To: David Miller <davem@davemloft.net>
Cc: takamiya@po.ntts.co.jp, herbert@gondor.apana.org.au,
	linux-crypto@vger.kernel.org
Subject: Re: [camellia-oss:00952] Re: [PATCH 5/5] camellia: de-unrolling, 64bit-ization
Date: Wed, 14 Nov 2007 00:38:31 -0700	[thread overview]
Message-ID: <200711140038.31859.vda.linux@googlemail.com> (raw)
In-Reply-To: <20071113.221041.47706914.davem@davemloft.net>

On Tuesday 13 November 2007 23:10, David Miller wrote:
> From: Denys Vlasenko <vda.linux@googlemail.com>
> Date: Tue, 13 Nov 2007 22:30:47 -0700
>
> > On Tuesday 13 November 2007 20:49, David Miller wrote:
> > > From: Denys Vlasenko <vda.linux@googlemail.com>
> > > Date: Tue, 13 Nov 2007 19:47:08 -0700
> > >
> > > > If CONFIG_CC_OPTIMIZE_FOR_SIZE is not an acceptable method,
> > > > do you have other ideas?
> > >
> > > Look at ways to make the code run faster without loop unrolling?
> >
> > I did it. I noticed that key setup is mostly operating on 64-bit
> > quantities, and provided alternative implementation which
> > exploits that fact. It's smaller and faster.
>
> Great, then you don't have to unroll the loop and performance
> is at least as good as before _and_ you save code space.

Unfortunately, it's applicable only to key setup,
and unrolling happens in actual encryption.

But the point still stands: irrespective of other optimizations,
unrolled and non-unrolled forms will still have different sizes
and speeds, and in some cases (like this one) you can't
pick one form which fits all.

> Please submit this new version :-)

Just did it. It's linux-2.6.23.1.camellia5.diff
--
vda

  reply	other threads:[~2007-11-14  7:38 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 11:43 [PATCH0/5] camellia: cleanup, de-unrolling, and 64bit-ization Denys Vlasenko
2007-10-25 11:45 ` [PATCH 1/5] camellia: cleanup Denys Vlasenko
2007-10-26  8:43   ` Noriaki TAKAMIYA
2007-11-06 14:17   ` Herbert Xu
2007-10-25 11:45 ` [PATCH 2/5] " Denys Vlasenko
2007-10-26  8:44   ` Noriaki TAKAMIYA
2007-11-06 14:19   ` Herbert Xu
2007-10-25 11:46 ` [PATCH 3/5] " Denys Vlasenko
2007-10-26  8:44   ` Noriaki TAKAMIYA
2007-11-06 14:21   ` Herbert Xu
2007-10-25 11:47 ` [PATCH 4/5] camellia: de-unrolling Denys Vlasenko
2007-10-26  8:45   ` Noriaki TAKAMIYA
2007-11-06 14:21   ` Herbert Xu
2007-10-25 11:48 ` [PATCH 5/5] camellia: de-unrolling, 64bit-ization Denys Vlasenko
2007-10-26  8:45   ` Noriaki TAKAMIYA
2007-11-06 14:23   ` Herbert Xu
2007-11-07 13:22     ` Denys Vlasenko
2007-11-08 13:30       ` Herbert Xu
2007-11-13  6:07         ` Noriaki TAKAMIYA
2007-11-13  6:25           ` [camellia-oss:00952] " Noriaki TAKAMIYA
2007-11-13 22:34             ` Denys Vlasenko
2007-11-14  1:41               ` David Miller
2007-11-14  2:47                 ` Denys Vlasenko
2007-11-14  3:49                   ` David Miller
2007-11-14  5:30                     ` Denys Vlasenko
2007-11-14  6:10                       ` David Miller
2007-11-14  7:38                         ` Denys Vlasenko [this message]
2007-11-14  7:15                       ` Denys Vlasenko
2007-11-14 14:14                         ` Herbert Xu
2007-11-14 21:28                           ` Denys Vlasenko
2007-11-18 13:21                             ` Herbert Xu
2007-11-19  4:30                               ` Denys Vlasenko
2007-11-19 18:49                                 ` Noriaki TAKAMIYA
2007-11-21  2:44                                   ` Denys Vlasenko
2007-11-21  3:53                                 ` Herbert Xu
2007-11-21  8:08                                   ` Denys Vlasenko
2007-11-21  8:12                                     ` Herbert Xu
2007-11-21  8:38                                       ` Denys Vlasenko
2007-11-14  4:18                   ` Noriaki TAKAMIYA
2007-10-25 11:57 ` [PATCH0/5] camellia: cleanup, de-unrolling, and 64bit-ization 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=200711140038.31859.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@po.ntts.co.jp \
    /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.