All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Vlasenko <vda.linux@googlemail.com>
To: Sebastian Siewior <linux-crypto@ml.breakpoint.cc>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	linux-crypto@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Crypto patches
Date: Sat, 20 Oct 2007 05:57:16 +0100	[thread overview]
Message-ID: <200710200557.17091.vda.linux@googlemail.com> (raw)
In-Reply-To: <20071018191940.GA11001@Chamillionaire.breakpoint.cc>

On Thursday 18 October 2007 20:19, Sebastian Siewior wrote:
> * Denys Vlasenko | 2007-10-18 12:28:13 [+0100]:
> 
> >I want to rediff and resend it. I also want to send patches
> >for other modules (e.g. camellia, aes).
> I'm going to unify the aes key setup on i386/x86_64/generic code on aes.
> It should work from what I thing but I am not sure :) Are planning/doing
> the same thing on aes?

I was thinking about measuring whether 64bit aes is really faster
than i386 one. i386 code seems to be already maxed out (at the first
glance), apart from using stack for temp storage. I wonder why
64bit one is completely different, and it worth testing -
maybe i386 code (only with saves to REX registers instead of stack)
will actually work faster in 64bit too.

But twofish and camellia are higher on my TODO list.
--
vda

      reply	other threads:[~2007-10-20  4:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 11:28 Crypto patches Denys Vlasenko
2007-10-18 15:03 ` Herbert Xu
2007-10-18 19:19 ` Sebastian Siewior
2007-10-20  4:57   ` Denys Vlasenko [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=200710200557.17091.vda.linux@googlemail.com \
    --to=vda.linux@googlemail.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@ml.breakpoint.cc \
    --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 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.