[asterisk-dev] nVidia Cuda

Matthew Rubenstein email at mattruby.com
Wed Mar 7 07:16:40 MST 2007

	Would you be willing to report which "top 4" functions take 40+40%? Or
at least a technique to test and identify them ourselves? Also, which
G.729 code: Digium, Intel, or some other?

On Wed, 2007-03-07 at 04:40 -0700, asterisk-dev-request at lists.digium.com
> Date: Wed, 7 Mar 2007 09:57:23 +0200
> From: "Stelios Koroneos" <skoroneos at digital-opsis.com>
> Subject: RE: [asterisk-dev] nVidia Cuda
> To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
> Message-ID: <HOECLKEKOHLAMMGDLLBHEEFDKFAA.skoroneos at digital-opsis.com>
> Content-Type: text/plain;       charset="iso-8859-7"
> G729 (and most codecs) spend a great amound of time in certain
> functions.
> In the g729 encoder a certain function takes close to 40% of the
> cycles
> required, while 3 more take another 40%
> Similar is the situation with the decoder.
> You don't need to get the entire codec in the GPU, just the parts that
> make
> a difference
> I have been working with g729 porting/acceleration for close to 5
> months now
> (fixpoint mainly for cpu's without fp)and also got into the CUDA dev
> program
> but did not find any time to do any actual work.
> I was able to get G729 accelerrated in a softcore/fpga combination
> with very
> good results
> I would also suggest, as others allready mentioned, to start "low", by
> using
> a simple encoder/decoder and try to see if you can speed it up,as it's
> a
> bitch to try to debug codecs in asterisk.
> Stelios S. Koroneos 

(C) Matthew Rubenstein

More information about the asterisk-dev mailing list