public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John Hawkes" <hawkes@sgi.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: "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>, "Jeremy Higdon" <jeremy@sgi.com>
Subject: Re: [PATCH] ia64: change usermode HZ to 250
Date: Wed, 28 Jun 2006 08:43:46 -0700	[thread overview]
Message-ID: <005e01c69ac9$a55e1bf0$6f00a8c0@comcast.net> (raw)
In-Reply-To: 1151483994.3153.5.camel@laptopd505.fenrus.org

From: "Arjan van de Ven" <arjan@infradead.org>
...
> ok why not define the userspace HZ to
>
> #define HZ sysconf(_SC_CLK_TCK)

That did occur to me.  It obviously does get the correct value.  The downside
is that one of those crufty apps that thinks it is using "HZ" as a constant
will instead be invoking a more costly syscall.  Should we care about the
resulting performance impact?

I vote for Arjan's solution.

John Hawkes


  reply	other threads:[~2006-06-28 15:46 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-28  8:39 ` Arjan van de Ven
2006-06-28 15:43   ` John Hawkes [this message]
2006-06-28 16:21     ` Alan Cox
2006-06-28 16:11       ` John Daiker
2006-06-28 16:50         ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
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 17:36 Luck, Tony
2006-06-29  9:37 ` Jes Sorensen
2006-06-29 11:02   ` 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 10:10                   ` Alan Cox
2006-07-11 18:37                   ` Jeremy Higdon
2006-07-12  2:02                     ` David Mosberger-Tang
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='005e01c69ac9$a55e1bf0$6f00a8c0@comcast.net' \
    --to=hawkes@sgi.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=djh@sgi.com \
    --cc=jeremy@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.com \
    --cc=tony.luck@gmail.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