linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: akpm@osdl.org, jan.glauber@de.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/13] s390: des crypto code cleanup.
Date: Fri, 13 Jan 2006 14:49:52 +0100	[thread overview]
Message-ID: <1137160192.6192.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20060113125808.GA1868@elf.ucw.cz>

On Fri, 2006-01-13 at 13:58 +0100, Pavel Machek wrote:
> On Čt 12-01-06 18:14:04, Martin Schwidefsky wrote:
> > From: Jan Glauber <jan.glauber@de.ibm.com>
> > 
> > [patch 1/13] s390: des crypto code cleanup.
> > 
> > Beautify the s390 in-kernel-crypto des code.
> > 
> > Signed-off-by: Jan Glauber <jan.glauber@de.ibm.com>
> > Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
> 
> Why does s390 need to do des in arch-specific code, BTW? Is it driver
> for some crypto accelerator or what?

Yes, the z900 and following machines have processor instructions to
speed up the crypto algorithms. There are instructions for sha1, sha256,
des and aes. They provide a good speedup, with the latest code des is up
to a factor of 40 faster than the software implementation.

-- 
blue skies,
   Martin

Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH



  reply	other threads:[~2006-01-13 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 17:14 [patch 1/13] s390: des crypto code cleanup Martin Schwidefsky
2006-01-13 12:58 ` Pavel Machek
2006-01-13 13:49   ` Martin Schwidefsky [this message]
2006-01-13 20:40   ` Arnd Bergmann

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=1137160192.6192.11.camel@localhost.localdomain \
    --to=schwidefsky@de.ibm.com \
    --cc=akpm@osdl.org \
    --cc=jan.glauber@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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).