public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fruhwirth Clemens <clemens@endorphin.org>
To: James Morris <jmorris@redhat.com>
Cc: Bill Davidsen <davidsen@tmr.com>, Dan Hollis <goemon@anime.net>,
	Venkat Manakkal <venkat@rayservers.com>,
	Andries Brouwer <aebr@win.tue.nl>,
	Paul Walker <paul@black-sun.demon.co.uk>,
	linux-kernel@vger.kernel.org, linux-crypto@nl.linux.org
Subject: Re: Announce loop-AES-v3.0b file/swap crypto package
Date: Wed, 19 Jan 2005 23:18:50 +0100	[thread overview]
Message-ID: <1106173131.19164.15.camel@ghanima> (raw)
In-Reply-To: <Xine.LNX.4.44.0501191623140.30540-100000@thoron.boston.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

On Wed, 2005-01-19 at 16:24 -0500, James Morris wrote: 
> On Wed, 19 Jan 2005, Fruhwirth Clemens wrote:
> 
> > I've rewritten some CBC code to fit the facilities I introduce in my LRW
> > patch[1]. Here are the results for my P4@1.8GHZ:
> > 
> > loop-aes, CBC: ~30.5mb/s
> > dm-crypt, CBC prior to my rewrite: ~23mb/s
> > dm-crypt, CBC with my LRW patch: ~27mb/s
> > dm-crypt, LRW with my LRW patch: ~27mb/s (slightly faster than CBC)
> > 
> > As you can see my LRW patches (actually it's the generic scatterwalker
> > which is part of the LRW patch set) halves the gap to loop-aes. 
> 
> This looks promising.  I wonder if the generic scatterwalker solves the 
> null encryption performance problem that was reported a little while back.

I've done some testing initially. The problem, at least with respect to
CBC, is that the NULL cipher's block size is 1. The CBC path isn't zero
originally and not even in my code (although I planned to do a zero copy
version). 

However, my patch will surely bring some relieve, as my scatterwalk code
does not give up the kmapping after every block, but wait for a page to
be completely processed. So that's one kmap/kunmap instead of 4096.

P.S.: The list of recipients have grown too long and topic moved a bit.
I will remove a bunch of people if I post another follow-up. Please
check the archive if interested and not subscribed.
-- 
Fruhwirth Clemens <clemens@endorphin.org>  http://clemens.endorphin.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-01-19 22:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-16 21:58 Announce loop-AES-v3.0b file/swap crypto package Jari Ruusu
2005-01-17  4:26 ` Bill Davidsen
2005-01-17  5:10   ` Willy Tarreau
2005-01-17 15:08   ` Jari Ruusu
2005-01-17 19:14     ` Fruhwirth Clemens
2005-01-17 19:29       ` Paul Walker
2005-01-17 21:04         ` Fruhwirth Clemens
2005-01-17 21:39           ` Paul Walker
2005-01-18 15:35           ` Jari Ruusu
2005-01-18 17:23             ` Andries Brouwer
2005-01-18 18:38               ` Venkat Manakkal
2005-01-19  0:18                 ` Dan Hollis
2005-01-19  0:46                   ` Kyle Moffett
2005-01-19 17:03                   ` Bill Davidsen
2005-01-19 17:57                     ` Fruhwirth Clemens
2005-01-19 21:24                       ` James Morris
2005-01-19 22:18                         ` Fruhwirth Clemens [this message]
2005-01-20 16:42                       ` Bill Davidsen
2005-01-17 21:26       ` markus reichelt
2005-01-17 23:11         ` Fruhwirth Clemens
2005-01-18  0:06           ` Daniel Harvey
2005-01-18 23:30             ` Peter_22
2005-01-18  9:49           ` jerome etienne
2005-01-18 15:36             ` Jari Ruusu
2005-01-20 22:38           ` markus reichelt
2005-01-21 18:29       ` Sytse Wielinga
2005-01-17 20:28     ` Andreas Jellinghaus
2005-01-17 21:38     ` Paul Walker

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=1106173131.19164.15.camel@ghanima \
    --to=clemens@endorphin.org \
    --cc=aebr@win.tue.nl \
    --cc=davidsen@tmr.com \
    --cc=goemon@anime.net \
    --cc=jmorris@redhat.com \
    --cc=linux-crypto@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@black-sun.demon.co.uk \
    --cc=venkat@rayservers.com \
    /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