All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian D. Carlstrom" <bdc@carlstrom.com>
To: Olof Johansson <olof@lixom.net>
Cc: 'Paul Mackerras' <paulus@samba.org>,
	'linuxppc-dev list' <linuxppc-dev@ozlabs.org>
Subject: Re: AltiVec in the kernel
Date: Thu, 20 Jul 2006 14:56:33 -0700	[thread overview]
Message-ID: <lezmf4j5ym.wl%bdc@carlstrom.com> (raw)
In-Reply-To: <20060720190523.GA27775@pb15.lixom.net>

At Thu, 20 Jul 2006 14:05:23 -0500, Olof Johansson wrote:
> On Thu, Jul 20, 2006 at 11:47:04AM -0700, Brian D. Carlstrom wrote:
> > A quick grep memcpy in the recent glibc sources on my linux/ppc box
> > seems to show no where near that level of optimization, but I admit
> > that I could have missed something.
> 
> http://penguinppc.org/dev/glibc/glibc-powerpc-cpu-addon.html

Very interesting. According to that page, the memcpy optimizations seem
to be using 64-bit operations and that 128-bit AltiVec operations are
still being solicited. 

I was encouraged to see the following: 

    If you need to build generic distributions (supporting several
    <cpu_types>) you can leverage the dl_procinfo support built into
    glibc. This mechanism allows for multiple versions of the core
    libraries (libc, libm, librt, libpthread, libpthread_db) to be
    stored in hardware/platform specific subdirectories under /lib[64].

However, I'm guessing this addon is not something found in common
distributions for PowerPC like Debian, Fedora, Gentoo, Ubuntu, ...

-bri

  reply	other threads:[~2006-07-20 21:56 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
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 [this message]
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=lezmf4j5ym.wl%bdc@carlstrom.com \
    --to=bdc@carlstrom.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    --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.