All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hellermann <stefan@the2masters.de>
To: Sebastian Siewior <linux-crypto@ml.breakpoint.cc>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [RFC] [crypto] padlock-aes loadkey ondemand
Date: Tue, 01 Apr 2008 20:38:46 +0200	[thread overview]
Message-ID: <47F28136.3080502@the2masters.de> (raw)
In-Reply-To: <20080330210152.GA25597@Chamillionaire.breakpoint.cc>

Sebastian Siewior schrieb:
> * Stefan Hellermann | 2008-03-30 21:03:18 [+0200]:
> 
>> Hi,
> Hi,
> 
>> I tested this patch with success, "512 bit key, 8192 byte blocks" is 29% faster!
> That's something.
> 
>> Thanks for this work!
> np :)
> 
>> Tested-By: Stefan Hellermann
>>
>> (Or what is the appropriate line here?)
> I thing that is okey if we add some numbers you provided.
> 
>> Here's tcrypt mode=200 output for xts without this patch
> As far as I remember you posted once some MiB/sec dm-crypt numbers the
> last time. Could you please post them as well since I don't which block
> size is the majority of the read/write request.

Now I have more numbers :)
read from a device through dm-crypt with aes-cts-plain, 256-bit mode (512bit keysize for
cryptsetup)
without this patch: 54MB/s with plain dd(blocksize 512b), 51MB/s with dd and a blocksize
of 512kib (Yes, it's slower with a larger blocksize!)
with this patch: 63MB/s with dd and a blocksize of 512b, 64MB/s with a blocksize of 512k
(This time the larger blocksize was a little bit faster in each test)
I did 5 tests for each combination, top shows everytime ~90% user and ~0% wait

Stefan

  reply	other threads:[~2008-04-01 18:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 22:33 [RFC] [crypto] padlock-aes loadkey ondemand Sebastian Siewior
2008-03-30 19:03 ` Stefan Hellermann
2008-03-30 21:01   ` Sebastian Siewior
2008-04-01 18:38     ` Stefan Hellermann [this message]
2008-04-02  6:44       ` Sebastian Siewior
2008-04-02  6:50         ` Herbert Xu
2008-04-02  7:17           ` Sebastian Siewior
2008-04-02  7:22             ` Herbert Xu
2008-08-07 14:53               ` Herbert Xu
2008-08-09 11:20                 ` Sebastian Siewior
2008-08-31  6:01                   ` Herbert Xu
2008-04-02 15:48           ` Stefan Hellermann
2008-04-09 16:38             ` Herbert Xu
2008-04-02  6:03 ` Herbert Xu
2008-04-02  6:26   ` Sebastian Siewior
2008-04-02  6:31     ` 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=47F28136.3080502@the2masters.de \
    --to=stefan@the2masters.de \
    --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.