From: linas@austin.ibm.com (Linas Vepstas)
To: Matt Sealey <matt@genesi-usa.com>
Cc: 'Olof Johansson' <olof@lixom.net>,
'linuxppc-dev list' <linuxppc-dev@ozlabs.org>,
'Paul Mackerras' <paulus@samba.org>
Subject: Re: AltiVec in the kernel
Date: Fri, 21 Jul 2006 11:51:30 -0500 [thread overview]
Message-ID: <20060721165130.GS5905@austin.ibm.com> (raw)
In-Reply-To: <000001c6acd3$ea93f5c0$99dfdfdf@bakuhatsu.net>
On Fri, Jul 21, 2006 at 09:42:32AM -0500, Matt Sealey wrote:
>
> > > http://penguinppc.org/dev/glibc/glibc-powerpc-cpu-addon.html
> >
> > 128-bit AltiVec operations are still being solicited.
>
> "Still"?
>
> http://www.freevec.org/
>
> Been there for months, before the glibc thing. Most of the functions
> are ready. Anyone can bugfix this. The beauty of GPL. The ugly part
> is.. we've had this there for months. Nobody has contributed a single
> update or bugfix or even a performance test as far as I know.
Sounds like a problem of advertising and communications. This is
kind of "under the radar" for most users and developers. It needs to
work out-of-the-box, most people, even those with interest in
performance, will not even be aware of the possibility to tne this.
It should be folded into glibc. It is up to the altivec product vendor
to nag the glibc folks into folding it in. This task could be as hard
as writing the code in the first place.
> Indeed it's a cute feature but we were scared away by the glibc guys
Many maintainers of core libraries have similar behaviour patterns.
Besides glibc, gcc and gsl come to mind. This is becase they get tired out
by naive eager-beavers who walk in with the greatest idea in the world,
make a big fuss about it, and the proceed to demonstrate that they have
absolutely no clue of what they're talking about. For every ten of
those, there's maybe one legit idea. Worse, many of these "clueless
newbies" come in the surprising shape of PhD's working outside thier
specialty, and can convingingly sling jargon and authority for a while
before its realized they're just... clueless.
If you've got good code, you'll just need to be persistent.
--linas
next prev parent reply other threads:[~2006-07-21 16:51 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
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 [this message]
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=20060721165130.GS5905@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.com \
--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 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).