public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alok Kataria <akataria@vmware.com>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Default HZ value for X86
Date: Mon, 27 Apr 2009 16:07:10 -0700	[thread overview]
Message-ID: <1240873630.14713.25.camel@alok-dev1> (raw)

Hi, 

I was wondering why do we still have the default HZ value as 1000 for
the x86 kernels.

arch/x86/configs/i386_defconfig:CONFIG_HZ=1000
arch/x86/configs/x86_64_defconfig:CONFIG_HZ=1000

With the highres timer implementation it was planned to move away from
relying on high timer interrupt frequency for applications requiring
precise high resolution timer's. 

This quote in the timer/hrtimers.txt also mentions that we should be
able to decrease the frequency of the timeout subsystem, which I assume
would mean reducing HZ value.

---------------------------------------------------------------------
"Another potential benefit is that such a separation allows even more
special-purpose optimization of the existing timer wheel for the low
resolution and low precision use cases - once the precision-sensitive
APIs are separated from the timer wheel and are migrated over to
hrtimers. E.g. we could decrease the frequency of the timeout subsystem
from 250 Hz to 100 HZ (or even smaller)."
---------------------------------------------------------------------

So, are there still any concerns that keep us from lowering the default
HZ value down to 250/100 for mainline ? 

Thanks,
Alok


             reply	other threads:[~2009-04-27 23:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 23:07 Alok Kataria [this message]
2009-04-27 23:34 ` Default HZ value for X86 Alan Cox
2009-04-28 16:55   ` Alok Kataria
2009-04-30 17:27   ` Artur Skawina
2009-04-30 18:24 ` Alok Kataria

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=1240873630.14713.25.camel@alok-dev1 \
    --to=akataria@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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