linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@breakpoint.cc>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Simon Richter <Simon.Richter@hogyros.de>, linuxppc-dev@lists.ozlabs.org
Subject: Re: AltiVec in the kernel
Date: Wed, 16 Dec 2009 23:11:52 +0100	[thread overview]
Message-ID: <20091216221152.GA11248@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <200912111649.25617.arnd@arndb.de>

* Arnd Bergmann | 2009-12-11 16:49:25 [+0100]:

>On Friday 11 December 2009, Simon Richter wrote:
>> Hi,
>> 
>> since there has been a thread on allowing the use of a coprocessor in
>> the kernel already: I am wondering if it'd make sense to use AltiVec for
>> AES in dm-crypt, and how difficult it would be to implement that.
>> 
>> I'm using a PegasosII which has a G4 running at 1 GHz; I get around 3
>> MB/s throughput when accessing harddisks. I think that could be
>> improved.
>> 
>> If I understand correctly, the actual encryption work runs in a kernel
>> thread, which is scheduled normally, so it ought to be possible to
>> enable AltiVec for that thread; am I missing something here?

dm-crypt is async these days so the patches Arnd mentioned could be
used actually :) I've never tested them with dm-crypt but it should
work. Back then I had around 20MiB/sec encryption and around 15 MiB/sec
for decryption on 4KiB page on a PS3 [0]. This was pure testing, no
subsystem was involved. dm-crypt will feed multiple 512 byte requests.
And according [1] 512 bytes are aren't slow :) However [2] says that
that AltiVec was always slower than the generic implementation. Maybe
PS3's AltiVec unit was slower than the average one because everyone was
focuesed on the SPUs. Maybe not and you get similar results. 

>Sebastian Siewior has implemented this some time ago:
>
>http://old.nabble.com/-RFC-0-3--Experiments-with-AES-AltiVec,-part-2-tc10034255.html
>
>You can try the old patches on your machine to see if they are any good
>there.
Ah you remember :)

[0] http://diploma-thesis.siewior.net/html/diplomarbeitch4.html#x12-46002r2
[1] http://diploma-thesis.siewior.net/html/diplomarbeitch4.html#x12-46004r4
[2] http://diploma-thesis.siewior.net/html/diplomarbeitch4.html#x12-47017r5
>
>	Arnd <><

Sebastian

  reply	other threads:[~2009-12-16 22:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 11:45 AltiVec in the kernel Simon Richter
2009-12-11 15:49 ` Arnd Bergmann
2009-12-16 22:11   ` Sebastian Andrzej Siewior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-18 12:48 Matt Sealey
2006-07-18 13:53 ` Kumar Gala
2006-07-18 15:10   ` Matt Sealey
2006-07-18 17:56     ` Paul Mackerras
2006-07-19 18:10       ` Linas Vepstas
2006-07-19 18:19         ` Paul Mackerras
2006-07-19 18:38           ` Johannes Berg
2006-07-19 18:57             ` Linas Vepstas
2006-07-20 12:31         ` Matt Sealey
2006-07-20 13:23           ` Kumar Gala
2006-07-20 13:33             ` Matt Sealey
2006-07-20 17:42           ` Linas Vepstas
2006-07-20 18:47             ` Brian D. Carlstrom
2006-07-20 19:05               ` Olof Johansson
2006-07-20 21:56                 ` Brian D. Carlstrom
2006-07-20 22:39                   ` Daniel Ostrow
2006-07-21  6:35                   ` Olof Johansson
2006-07-21 14:42                   ` Matt Sealey
2006-07-21 16:51                     ` Linas Vepstas
2006-07-21 18:08                       ` Matt Sealey
2006-07-22  3:09                         ` Segher Boessenkool
2006-07-23 13:28                           ` Matt Sealey
2006-07-23 21:37                             ` Benjamin Herrenschmidt
2006-07-21 18:46                       ` Brian D. Carlstrom
2006-07-21 21:30                       ` Hollis Blanchard
2006-07-21 22:21                   ` Peter Bergner
2006-07-18 18:39     ` Benjamin Herrenschmidt
2006-07-18 17:43 ` Paul Mackerras

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=20091216221152.GA11248@Chamillionaire.breakpoint.cc \
    --to=bigeasy@breakpoint.cc \
    --cc=Simon.Richter@hogyros.de \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@lists.ozlabs.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).