linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kaspar <zkaspar82@gmail.com>
To: linux-crypto@vger.kernel.org
Subject: Re: serpent-sse2 - different key size same speed?
Date: Tue, 20 Mar 2012 09:08:22 +0100	[thread overview]
Message-ID: <4F683AF6.30400@gmail.com> (raw)
In-Reply-To: <20120320085319.19374u25s60oh1gk@www.81.fi>

Dne 20.3.2012 7:53, Jussi Kivilinna napsal(a):
> Quoting Zdenek Kaspar <zkaspar82@gmail.com>:
> 
>> Hello everyone,
>>
>> I just quick tested 3.3.0 kernel (x86_64) to get idea how serpent-sse2
>> implementation works on Core2 machine. My dirty testing revealed that
>> key size doesn't have impact on speed. Is such behavior normal ?
> 
> It's expected result, serpent speed does not depend on key-size and for
> example twofish and blowfish are another such ciphers where speed is
> key-size independent.
> 
> -Jussi

Thanks for clarification and enlighten me :) (btw: nice work with
serpent-sse2)

Z.

      reply	other threads:[~2012-03-20  8:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 18:06 serpent-sse2 - different key size same speed? Zdenek Kaspar
2012-03-20  6:53 ` Jussi Kivilinna
2012-03-20  8:08   ` Zdenek Kaspar [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=4F683AF6.30400@gmail.com \
    --to=zkaspar82@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).