public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Mosberger-Tang" <David.Mosberger@acm.org>
To: Jeremy Higdon <jeremy@sgi.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Jes Sorensen <jes@sgi.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Luck, Tony" <tony.luck@intel.com>,
	John Daiker <jdaiker@osdl.org>, John Hawkes <hawkes@sgi.com>,
	Tony Luck <tony.luck@gmail.com>, Andrew Morton <akpm@osdl.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jack Steiner <steiner@sgi.com>, Dan Higgins <djh@sgi.com>
Subject: Re: [PATCH] ia64: change usermode HZ to 250
Date: Wed, 12 Jul 2006 02:02:37 +0000	[thread overview]
Message-ID: <ed5aea430607111902i91b9e92s784ce8d2103f1b4e@mail.gmail.com> (raw)
In-Reply-To: <20060711183754.GB734242@sgi.com>

On 7/11/06, Jeremy Higdon <jeremy@sgi.com> wrote:

> Okay.  So what do you think about changing the value in param.h from
> 1024, so that it matches the new common value of 250, or is it best
> just to leave it at 1024 and let applications that use it get the wrong
> result?

In my opinion, HZ needs to be a constant, since otherwise you could
break perfectly fine existing code (e.g., code which statically
initializes a variable with HZ and then picks up the correct frequency
from sysconf) and if you have to pick a particular constant, it seems
reasonable to me to pick the most commonly used frequency (which
appears to be 250Hz at the moment).

  --david
-- 
Mosberger Consulting LLC, http://www.mosberger-consulting.com/

  reply	other threads:[~2006-07-12  2:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 22:01 [PATCH] ia64: change usermode HZ to 250 hawkes
2006-06-27 22:26 ` Luck, Tony
2006-06-27 23:09   ` Lee Revell
2006-06-28  8:43   ` Arjan van de Ven
2006-06-28 10:47     ` Alan Cox
2006-06-28 10:34       ` Arjan van de Ven
2006-06-28 14:46         ` Christoph Lameter
2006-06-28  8:39 ` Arjan van de Ven
2006-06-28 15:43   ` John Hawkes
2006-06-28 16:21     ` Alan Cox
2006-06-28 16:11       ` John Daiker
2006-06-28 16:50         ` Alan Cox
2006-06-28 17:36 ` Luck, Tony
2006-06-29  9:37   ` Jes Sorensen
2006-06-29 10:46     ` Alan Cox
2006-06-29 10:48       ` Jes Sorensen
2006-06-29 10:55         ` Arjan van de Ven
2006-06-29 12:56           ` Jes Sorensen
2006-07-08  0:14           ` Jeremy Higdon
2006-07-08  2:51             ` Tony Luck
2006-07-08  6:42             ` Arjan van de Ven
2006-07-08 13:07               ` David Mosberger-Tang
2006-07-10 20:22                 ` Jeremy Higdon
2006-07-11  3:01                   ` David Mosberger-Tang
2006-07-11  9:53                     ` Alan Cox
2006-07-11 18:37                     ` Jeremy Higdon
2006-07-12  2:02                       ` David Mosberger-Tang [this message]
2006-06-29 11:34         ` Alan Cox
2006-06-29 14:09 ` Albert Cahalan
2006-07-09 19:18 ` Luck, Tony

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=ed5aea430607111902i91b9e92s784ce8d2103f1b4e@mail.gmail.com \
    --to=david.mosberger@acm.org \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=djh@sgi.com \
    --cc=hawkes@sgi.com \
    --cc=jdaiker@osdl.org \
    --cc=jeremy@sgi.com \
    --cc=jes@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.com \
    --cc=tony.luck@gmail.com \
    --cc=tony.luck@intel.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