public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: David Lang <dlang@digitalinsight.com>
Cc: Sven-Thorsten Dietrich <sven@mvista.com>,
	thockin@hockin.org, Lee Revell <rlrevell@joe-job.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Dual core Athlons and unsynced TSCs
Date: Sat, 14 Jan 2006 02:21:23 +0100	[thread overview]
Message-ID: <43C85213.40808@domdv.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0601131701590.9821@qynat.qvtvafvgr.pbz>

David Lang wrote:
[snip]
> I'm not saying it's the right answer, but it's one of two workarounds
> currently available.
> 
> idle=poll causes increased power useage
> 
> timer source change (mentioned earlier in this thread) limits timer
> precision
> 
> neither of these are fixes, but by understanding the different costs
> people can choose the work around they want to use while waiting for a
> better fix.

The problem being that some of us use their laptops for audio work too.
And then high battery usage, noisy fans or lack of high res timers will
be really bad.

Simple example:
I do final mastering work using my laptop and Ardour/Jack/JAMin out of
house in a place with a good stage audio system (Mackie mixer, 2KW
Dynacord Amp/Syrincs S3) and a sufficient listening space to get a
proper bass mix. I run on battery in this case to avoid any kind of
audio interference (ground loops, etc). Now thinking of a dual core
laptop...
-- 
Andreas Steinmetz                       SPAMmers use robotrap@domdv.de

  reply	other threads:[~2006-01-14  1:21 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 22:17 Dual core Athlons and unsynced TSCs Lee Revell
2006-01-13 15:10 ` Roger Heflin
2006-01-13 16:04   ` Steven Rostedt
2006-01-13 17:47     ` Lee Revell
2006-01-13 17:52       ` Steven Rostedt
2006-01-13 17:54         ` Lee Revell
2006-01-13 18:41           ` Steven Rostedt
2006-01-13 18:55             ` Lee Revell
2006-01-13 20:09               ` Steven Rostedt
2006-01-13 20:26                 ` Steven Rostedt
2006-01-13 20:40                   ` Lee Revell
2006-01-13 20:43                   ` Lee Revell
2006-01-13 20:46                     ` Thomas Gleixner
2006-01-13 20:48                       ` Lee Revell
2006-01-13 20:51                         ` Thomas Gleixner
2006-01-13 20:52                         ` Steven Rostedt
2006-01-13 21:05                       ` Steven Rostedt
2006-01-13 21:10                         ` Thomas Gleixner
2006-01-13 21:17                           ` Steven Rostedt
2006-01-16  9:52                             ` Thomas Gleixner
2006-01-16 15:55                               ` Steven Rostedt
2006-01-14  0:23                 ` john stultz
2006-01-14  1:10                   ` Steven Rostedt
2006-01-14  1:14                     ` Lee Revell
2006-01-14  1:23                       ` john stultz
2006-01-14  1:27                         ` Lee Revell
2006-01-14  1:39                           ` john stultz
2006-01-14  1:43                             ` Steven Rostedt
2006-01-14  1:50                               ` john stultz
2006-01-14  2:15                                 ` Steven Rostedt
2006-01-14  2:34                                 ` Steven Rostedt
2006-01-16  1:19                             ` Andi Kleen
2006-01-14  6:54               ` Christoph Lameter
2006-01-13 18:06 ` thockin
2006-01-13 17:58   ` Lee Revell
2006-01-13 18:16     ` thockin
2006-01-13 18:09       ` Lee Revell
2006-01-13 18:55         ` thockin
2006-01-13 18:56           ` Sven-Thorsten Dietrich
2006-01-13 19:00             ` Lee Revell
2006-01-13 19:07               ` Sven-Thorsten Dietrich
2006-01-13 21:18               ` David Lang
2006-01-13 21:56                 ` thockin
2006-01-13 22:05                   ` David Lang
2006-01-13 22:18                     ` Sven-Thorsten Dietrich
2006-01-13 22:49                       ` David Lang
2006-01-14  0:41                         ` Andreas Steinmetz
2006-01-14  1:04                           ` David Lang
2006-01-14  1:21                             ` Andreas Steinmetz [this message]
2006-01-14  1:51                               ` thockin
2006-01-15  8:52                             ` Zan Lynx
2006-01-15 16:25                               ` thockin
2006-01-15 16:33                                 ` Lee Revell
2006-01-15 18:21                                   ` thockin
2006-01-15 18:29                                     ` Lee Revell
2006-01-15 18:49                                       ` thockin
2006-01-14  1:13                           ` thockin
2006-01-13 22:23                     ` thockin
2006-01-13 19:13             ` Xavier Bestel
2006-01-13 19:32             ` thockin
2006-01-13 20:58               ` Steven Rostedt
     [not found] <5ujmj-1UQ-511@gated-at.bofh.it>
     [not found] ` <5uBnF-2SG-11@gated-at.bofh.it>
     [not found]   ` <5uBnF-2SG-9@gated-at.bofh.it>
     [not found]     ` <5uBxi-3iM-21@gated-at.bofh.it>
     [not found]       ` <5uBGY-3ul-21@gated-at.bofh.it>
     [not found]         ` <5uCa5-443-45@gated-at.bofh.it>
     [not found]           ` <5uCjF-4fW-15@gated-at.bofh.it>
     [not found]             ` <5uCtj-4Fi-15@gated-at.bofh.it>
2006-01-14  0:24               ` Robert Hancock

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=43C85213.40808@domdv.de \
    --to=ast@domdv.de \
    --cc=dlang@digitalinsight.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=sven@mvista.com \
    --cc=thockin@hockin.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