All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [REANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin
Date: Tue, 14 Jul 2015 21:36:11 +0500	[thread overview]
Message-ID: <55A53A7B.20806@gmail.com> (raw)
In-Reply-To: <20150714161711.GB11162@sirena.org.uk>

14.07.2015 21:17, Mark Brown wrote:
> On Tue, Jul 14, 2015 at 09:04:30PM +0500, Alexander E. Patrakov wrote:
>
>> I would like to see some direct measurements related to recent power-saving
>> proposals, including the "disable rewinds" flag. Myself, I can redo
>> battery-life measurements on Intel-based laptops that my colleagues have,
>> and maybe compare dmix, PulseAudio and CRAS in terms of power consumption.
>
> The numbers I seem to remember seeing at the time were these IIRC:
>
>     http://linux-tipps.blogspot.co.uk/2011/04/power-performance-of-pulseaudio-alsa.html
>
> saying there was a 0.4W win (I think Arun had some similar numbers).

Thanks for the link. I have no reason to doubt these measurements. Note, 
however, that they are of the "pulseaudio vs pulseaudio" type, and give 
no insight into the structure of the win. By "structure", I mean the 
proportion of energy wasted due to the wakeup itself, in the kernel 
code, and in the pulseaudio code. IOW, they, technically, don't rule out 
the "pulseaudio is inefficient at low latencies, and that's pulseaudio's 
fault" possibility. That's why (and also because, on my hardware, the 
win with hw:0 and aplay is smaller) I want to do some cross-comparisons 
of various sound servers to the raw hw:0 device. It would also be nice 
to be able to see directly the effect of David's work on srbchannel.

-- 
Alexander E. Patrakov

  reply	other threads:[~2015-07-14 16:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 15:03 [REANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin Mark Brown
2015-07-14 16:04 ` Alexander E. Patrakov
2015-07-14 16:17   ` Mark Brown
2015-07-14 16:36     ` Alexander E. Patrakov [this message]
2015-07-14 17:05       ` Alexander E. Patrakov
2015-07-27 23:26   ` Pierre-Louis Bossart
2015-07-18 17:07 ` Vinod Koul
2015-09-10 21:35   ` Eric Laurent
2015-09-14 18:02     ` Mark Brown
2015-09-14 18:10       ` Eric Laurent
2015-07-21 11:29 ` Bard Liao
2015-07-27 23:05   ` Pierre-Louis Bossart
2015-08-03  3:15     ` Vinod Koul
2015-09-22  8:49       ` Arun Raghavan
2015-10-03 16:13         ` Takashi Iwai
2015-10-04 22:57           ` Mark Brown
2015-10-04 23:19             ` Mark Brown
2015-10-04  9:24         ` Arun Raghavan
2015-08-01  7:37 ` Lars-Peter Clausen
2015-08-03  3:21   ` Vinod Koul
2015-08-04 16:13     ` Mark Brown
2015-08-05  2:56       ` Vinod Koul
2015-08-05  9:39         ` Mark Brown
2015-08-03 19:11   ` Pierre-Louis Bossart
2015-08-04 16:03   ` Mark Brown
2015-08-04 18:50     ` Lars-Peter Clausen

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=55A53A7B.20806@gmail.com \
    --to=patrakov@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.