public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Siarhei Siamashka <siarhei.siamashka@nokia.com>
To: "ext Brad Midgley" <bmidgley@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH/RFC] SIMD optimizations for SBC encoder analysis filter
Date: Fri, 2 Jan 2009 19:11:20 +0200	[thread overview]
Message-ID: <200901021911.20265.siarhei.siamashka@nokia.com> (raw)
In-Reply-To: <d89ddf300901020827w20c48a5fgb37d35ff33ea5fd3@mail.gmail.com>

On Friday 02 January 2009 18:27:33 ext Brad Midgley wrote:
> Siarhei
>
> > I wonder what CPU architectures are the most important for bluez?
>
> This is not an easy question, but one perspective is to consider the
> impact on battery life. Running sbc encoding on a phone will have a
> greater impact on battery life than it does to run it on a laptop.

I see. I'm mostly interested in ARM, so this one should be quite fine. On the
other hand, if we sacrifice performance let's say for MIPS when adding
some of the changes beneficial for other platforms, will it be considered an
important regression?

I also submitted MMX implementation first as this is the code which can be
hopefully tested by more people. Anyway, the most hard part was to transform
the code to be efficiently vectorizable (done by writing several additional
scripts which were used to find an optimal input data permutation and generate
the tables). After that, just converting C code to the appropriate MMX
instructions in gcc inline assembly took probably only ~1 day of working time,
including testing. Support for the other architectures should be quite easy
from this point (ARM will follow next).

> The ideal is to have portable devices mitigate this with dsp hardware,
> but we can't count on the hardware or the driver to be there in all
> cases. (see https://garage.maemo.org/projects/dsp-sbc/ for some work
> using the TI dsp)

Yes, I know about this project. And its maintainer should be subscribed here
too :)

Making code a bit more C55x friendly is not difficult at all and can be surely
done.

-- 
Best regards,
Siarhei Siamashka

  reply	other threads:[~2009-01-02 17:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-31 16:03 [PATCH/RFC] SIMD optimizations for SBC encoder analysis filter Siarhei Siamashka
2008-12-31 20:55 ` Luiz Augusto von Dentz
2009-01-02 16:33   ` Siarhei Siamashka
2009-01-02 19:40     ` Luiz Augusto von Dentz
2009-01-04 17:56       ` Siarhei Siamashka
2009-01-06  2:50   ` Marcel Holtmann
2009-01-01  8:58 ` Marcel Holtmann
2009-01-02 16:07   ` Siarhei Siamashka
2009-01-02 16:27     ` Brad Midgley
2009-01-02 17:11       ` Siarhei Siamashka [this message]
2009-01-02 18:03         ` Brad Midgley
2009-01-05 11:08         ` Simon Pickering
2009-01-05  8:57     ` Siarhei Siamashka
2009-01-06  2:49     ` Marcel Holtmann
2009-01-06  5:27       ` Christian Hoene
2009-01-06  5:45         ` Marcel Holtmann
2009-01-07  9:31           ` Siarhei Siamashka
2009-01-09 16:50       ` Siarhei Siamashka
2009-01-15 19:34         ` Siarhei Siamashka
2009-01-15 23:29           ` Marcel Holtmann

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=200901021911.20265.siarhei.siamashka@nokia.com \
    --to=siarhei.siamashka@nokia.com \
    --cc=bmidgley@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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