linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Grover, Andrew" <andrew.grover@intel.com>
To: "Jean-Marc Valin" <Jean-Marc.Valin@USherbrooke.ca>,
	"Martin J. Bligh" <mbligh@aracnet.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: RE: Increasing HZ (patch for HZ > 1000)
Date: Thu, 11 Dec 2003 11:22:19 -0800	[thread overview]
Message-ID: <F760B14C9561B941B89469F59BA3A84702C931A4@orsmsx401.jf.intel.com> (raw)

> From: linux-kernel-owner@vger.kernel.org 
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of 
> Jean-Marc Valin
> > Why would you want to *increase* HZ? I'd say 1000 is 
> already too high
> > personally, but I'm curious what you'd want to do with it? Embedded
> > real-time stuff?
> 
> Actually, my reasons may sound a little strange, but basically I'd be
> fine with HZ=1000 if it wasn't for that annoying ~1 kHz sound when the
> CPU is idle (probably bad capacitors). By increasing HZ to 10 kHz, the
> sound is at a frequency where the ear is much less sensitive. 
> Anyway, I
> thought some people might be interested in high HZ for other (more
> fundamental) reasons, so I posted the patch.

I'd advocate lower HZ. Say, oh I dunno...100? This is better for power
management and also should make the sound go away.

Hmm, I wonder if HZ=10 would break anything :)

Regards -- Andy

             reply	other threads:[~2003-12-11 19:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 19:22 Grover, Andrew [this message]
2003-12-12 22:31 ` Increasing HZ (patch for HZ > 1000) Jamie Lokier
2003-12-12 22:58   ` Vojtech Pavlik
2003-12-12 23:45     ` Jamie Lokier
2003-12-13  8:36       ` Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
2003-12-12 15:52 Vincent Legoll
2003-12-11  6:05 Jean-Marc Valin
2003-12-11  7:07 ` Martin J. Bligh
2003-12-11  7:15   ` Jean-Marc Valin
2003-12-11  7:18     ` Martin J. Bligh
2003-12-11 17:18       ` Gene Heskett
2003-12-11 17:33         ` Martin J. Bligh
2003-12-11 18:10           ` Richard B. Johnson
2003-12-11 19:14             ` Gene Heskett
2003-12-11 18:35           ` Gene Heskett
2003-12-12 22:08       ` Pavel Machek
2003-12-12 22:57         ` Jean-Marc Valin
2003-12-12 23:18           ` Måns Rullgård
2003-12-12 23:40           ` Pavel Machek
2003-12-13  2:25             ` Måns Rullgård
2003-12-16  3:04             ` john stultz
2003-12-16  5:20               ` Mitchell Blank Jr
2003-12-14  1:05           ` bill davidsen
2003-12-14  4:48             ` Pat Erley
2003-12-11  7:30     ` Nick Piggin
2003-12-11  8:25     ` Tim Schmielau
2003-12-12  8:00   ` Jean-Marc Valin
2003-12-12 22:10     ` Pavel Machek
2003-12-12 22:50       ` Jean-Marc Valin
2004-01-03 18:16         ` Bill Davidsen
     [not found]         ` <010f01c415a4_27033d00_d100000a@sbs2003.local>
2004-04-06 13:00           ` Pavel Machek

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=F760B14C9561B941B89469F59BA3A84702C931A4@orsmsx401.jf.intel.com \
    --to=andrew.grover@intel.com \
    --cc=Jean-Marc.Valin@USherbrooke.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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;
as well as URLs for NNTP newsgroup(s).