All of lore.kernel.org
 help / color / mirror / Atom feed
From: linas@austin.ibm.com (Linas Vepstas)
To: Paul Mackerras <paulus@samba.org>
Cc: 'linuxppc-dev list' <linuxppc-dev@ozlabs.org>
Subject: Re: AltiVec in the kernel
Date: Wed, 19 Jul 2006 13:10:47 -0500	[thread overview]
Message-ID: <20060719181047.GL5905@austin.ibm.com> (raw)
In-Reply-To: <17597.8378.972640.464219@cargo.ozlabs.ibm.com>


On Wed, Jul 19, 2006 at 03:56:10AM +1000, Paul Mackerras wrote:
> A lot of compression and encryption algorithms, by their very nature,
> are very difficult to parallelize enough to get any significant
> improvement from altivec.  I looked at SHA1 for instance, and the
> sequential dependencies in the computation are such that it is
> practically impossible to find a way to do 4 things in parallel.  The
> sequential dependencies are of course a critical part of the way that
> SHA1 ensures that a small change in any part of the input data results
> in substantial changes in every byte of the output.

But perhaps, in principle, couldn't one run four independent streams 
in parallel?  Thus, for example, on an SSL-enabled web server, one 
could service multiple encryption/decryption threads at once. 

In practice, I don't beleive the infrastructure for that kind of
parallelism is in place. I'm struggling to find a reason to develop
that kind of infrastructure. Mumble something about Cell. 

> I think that there are actually very few places in the kernel where we
> are doing something which is parallelizable, sufficiently
> compute-intensive, and not bound by memory bandwidth, to be worth
> using altivec.

Yes.

As to non-kernel applications, is there anything for GMP (the 
Gnu Multi-Precision library, an arbitrary-precision math library)
on the Altivec? How aout the Cell?

--linas

  reply	other threads:[~2006-07-19 18:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 12:48 AltiVec in the kernel 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2009-12-11 11:45 Simon Richter
2009-12-11 15:49 ` Arnd Bergmann
2009-12-16 22:11   ` Sebastian Andrzej Siewior

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=20060719181047.GL5905@austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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.