From: "Luiz Augusto von Dentz" <luiz.dentz@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] PATCH2/2: bluez-utils - avoid-unnecessary-polls
Date: Sun, 14 Oct 2007 00:21:06 -0300 [thread overview]
Message-ID: <2d5a2c100710132021o60ae76auf64c6cb5cfe702db@mail.gmail.com> (raw)
In-Reply-To: <000401c80ccb$a7cb44b0$c72915ac@NOE.Nokia.com>
Hi Kai,
On 10/12/07, Kai Vehmanen <kai.vehmanen@nokia.com> wrote:
> Hello again,
>
> here's the second patch to ALSA A2DP plugin in bluez-utils
> (see my previous mail).
>
> This patch changes the worker thread poll timeout to be
> calculated according to application chosen period size.
> This allows to decrease the CPU load significantly for those
> applications that do not require an ultra small period
> size. Without the patch (poll timeout of 1msec), the system
> call load is pretty heavy...
This was done before but I guess for some reason I don't remember
now we remove it in favor of fixed timeout. Thought we should
reconsider it if it has a good impact on CPU load.
-- =
Luiz Augusto von Dentz
Engenheiro de Computa=E7=E3o
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-10-14 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 12:30 [Bluez-devel] PATCH2/2: bluez-utils - avoid-unnecessary-polls Kai Vehmanen
2007-10-14 3:21 ` Luiz Augusto von Dentz [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=2d5a2c100710132021o60ae76auf64c6cb5cfe702db@mail.gmail.com \
--to=luiz.dentz@gmail.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