From: Bill Davidsen <davidsen@tmr.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>,
"Kernel," <linux-kernel@vger.kernel.org>
Subject: Re: [BUG 2579] linux 2.6.* sound problems (SOLVED)
Date: Tue, 01 Nov 2005 16:44:42 -0500 [thread overview]
Message-ID: <4367E1CA.9040400@tmr.com> (raw)
In-Reply-To: <1130872775.22089.1.camel@mindpipe>
Lee Revell wrote:
> On Tue, 2005-11-01 at 18:18 +0100, Patrizio Bassi wrote:
>
>>Jeffrey Hundstad ha scritto:
>>
>>
>>>Since you're going to 250 Hz. Please, if you would, see if you can
>>>tell any performance change and report that as well. I'm more than a
>>>little skeptical that you'll notice. BTW: Your battery life should be
>>>a little better at 100 Hz also.
>>>
>>
>>sincerely i can notice that task and application switching is a bit slower.
>>i have a 500mhz cpu so i think i can notice a bit the difference.
>>i can't estimate it mmm...
>>i'll say no more that 5-8%.
>>but i don't know where i'm gaining speed..
>
>
> Um, wasn't a consensus reached at OLS two years ago that the target for
> desktop responsiveness would be 1ms which is impossible with HZ=100 or
> 250?
Go back and reread the thread in the archives. The short answer is that
he who controls the code controls the decisions. I just fix it
everywhere, since 250 is too fast for optimal battery life, too slow for
optimal response or multimedia, and not optimal for any server
application I run (usenet, dns, mail, http, firewall).
A perfect compromise is one which makes everyone reasonably happy; this
is like the XOR of that, it leaves everyone slightly dissatisfied. ;-)
I'm convinced that Linus choose this value to make everyone slightly
unhappy, so development of various variable rate and tick skipping
projects would continue. Unfortunately that doesn't seem to have
happened :-(
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-11-01 21:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53JVy-4yi-19@gated-at.bofh.it>
2005-10-31 16:43 ` [BUG 2579] linux 2.6.* sound problems Bodo Eggert
[not found] ` <53Kyw-5Bt-53@gated-at.bofh.it>
[not found] ` <53L26-6dC-75@gated-at.bofh.it>
2005-10-31 16:59 ` Patrizio Bassi
2005-10-31 17:04 ` Patrizio Bassi
2005-10-31 17:27 ` Ray Lee
[not found] ` <53Lus-73L-39@gated-at.bofh.it>
2005-10-31 19:38 ` Patrizio Bassi
[not found] ` <545a6-2GZ-17@gated-at.bofh.it>
2005-11-01 16:45 ` [BUG 2579] linux 2.6.* sound problems (SOLVED) Patrizio Bassi
[not found] ` <43679FFB.6040504@mnsu.edu>
2005-11-01 17:18 ` Patrizio Bassi
2005-11-01 19:19 ` Lee Revell
2005-11-01 21:44 ` Bill Davidsen [this message]
2005-11-01 23:28 ` Kyle Moffett
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=4367E1CA.9040400@tmr.com \
--to=davidsen@tmr.com \
--cc=jeffrey.hundstad@mnsu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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