From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Nokia 770 and bluetooth audio
Date: Sun, 09 Oct 2005 09:49:17 -0600 [thread overview]
Message-ID: <43493BFD.1060300@xmission.com> (raw)
In-Reply-To: <1128860708.8700.12.camel@localhost.localdomain>
Victor
> It would be nice to have at least a piece of advise from those
> mysterious people who tell all those things about the optimization :)
as far as the algorithm goes, I decided for the decoder that there were
basically two paths you could go down for optimizing:
- keep the shifting of values around in each pass and unroll the loops
(in this case referencing the tables is optimized by the compiler to
literal values so unrolling eliminates an array access)
- eliminate the shifting of values and don't unroll the loop, just
simplify the array index computations (the table access is different in
each pass depending on where the data would have been shifted around to
so unrolling is no win)
I ended up moving 8-subbands to the latter and I will move 4 too.
For the decoder it's moot since anyone serious about decoding will be
doing it in CSR silicon, but there may be a parallel in the encoder.
Brad
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-10-09 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 22:35 [Bluez-devel] Nokia 770 and bluetooth audio Brad Midgley
2005-10-08 12:33 ` Marcel Holtmann
2005-10-09 5:48 ` Brad Midgley
2005-10-09 9:14 ` Marcel Holtmann
2005-10-09 12:25 ` Victor Shchebatyuk
2005-10-09 13:22 ` Marcel Holtmann
2005-10-09 15:49 ` Brad Midgley [this message]
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=43493BFD.1060300@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
/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).