mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Lee Revell <rlrevell@joe-job.com>,
	Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>,
	"Kernel," <linux-kernel@vger.kernel.org>
Subject: Re: [BUG 2579] linux 2.6.* sound problems (SOLVED)
Date: Tue, 1 Nov 2005 18:28:20 -0500	[thread overview]
Message-ID: <C40C872A-9CE5-4832-94B6-FAC26A403AF7@mac.com> (raw)
In-Reply-To: <4367E1CA.9040400@tmr.com>

On Nov 1, 2005, at 16:44:42, Bill Davidsen wrote:
> 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 :-(

No, I think it's been happening, it's just that said developers are  
still fixing the copious bugs in the various kernel concepts of  
"time".  IIRC John Stultz' rework is approaching completion, and when  
that goes in it makes life a lot easier for the various dyntick and  
variable tick projects.

Cheers,
Kyle Moffett

--
Unix was not designed to stop people from doing stupid things,  
because that would also stop them from doing clever things.
   -- Doug Gwyn



      reply	other threads:[~2005-11-01 23:28 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
2005-11-01 23:28             ` Kyle Moffett [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=C40C872A-9CE5-4832-94B6-FAC26A403AF7@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=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

all inboxes | Powered by JetHome®