From: Pavel Machek <pavel@ucw.cz>
To: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Increasing HZ (patch for HZ > 1000)
Date: Sat, 13 Dec 2003 00:40:29 +0100 [thread overview]
Message-ID: <20031212234028.GA541@elf.ucw.cz> (raw)
In-Reply-To: <1071269849.4182.14.camel@idefix.homelinux.org>
Hi!
> > Every notebook from thinkpad 560X up has produced some kind of
> > cpu-load-related-noise. You'd have to throw out quite a lot of
> > notebooks...
>
> You're right, I'm probably not the only one. It may be worth at least
> having an option to change HZ to less annoying values. Otherwise there
> are going to be lots of complaints when people try out 2.6 on their
> laptops and hear that noise. On mine, I seriously could not stand the
> noise more than 5 minutes. Not because it was that loud but 1 kHz is
> really annoying.
Okay, we are probably taking other sounds. I can hear cpu-load-related
noise on every notebook from thinkpad 560X -- in a quiet room, and on
some machines its rather hard to notice. You probably have way more
annoying problem.
> > PS: Jean, can you try how high you can get it? You might want to go to
> > 24kHz so that no human can hear it, or to 100kHz to be kind to
> > cats. At ~1MHz you'd be even kind to bats :-), but it is probably
> > impossible to get over 200kHz or so. Still it might be funny
> > experiment.
>
> For now, my patch only allows up to around 10 kHz. At that frequency, I
> don't hear anything because the noise is not loud enough (ear is much
> more sensitive at 1 kHz). Also, I have around 10% overhead on my
> Pentium-M 1.6 GHz, so I guess it's not for everyone. Extrapolating from
> there, I'd also say that at 100 kHz, it wouldn't do anything but handle
> the interrupts, which is slightly annoying when you want to actually get
> some work done :)
I wonder what happens at 200kHz then; system might detect some lost
ticks and keep running at very slow speed...
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-12-12 23:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 6:05 Increasing HZ (patch for HZ > 1000) 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 [this message]
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
2003-12-11 19:22 Grover, Andrew
2003-12-12 22:31 ` Jamie Lokier
2003-12-12 22:58 ` Vojtech Pavlik
2003-12-12 23:45 ` Jamie Lokier
2003-12-13 8:36 ` Vojtech Pavlik
2003-12-12 15:52 Vincent Legoll
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=20031212234028.GA541@elf.ucw.cz \
--to=pavel@ucw.cz \
--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).