From: Jes Sorensen <jes@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"John Daiker" <jdaiker@osdl.org>, "John Hawkes" <hawkes@sgi.com>,
"Arjan van de Ven" <arjan@infradead.org>,
"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: 29 Jun 2006 05:37:40 -0400 [thread overview]
Message-ID: <yq04py4i9p7.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2A27FC5F@scsmsx411.amr.corp.intel.com>
>>>>> "Tony" == Luck, Tony <tony.luck@intel.com> writes:
Tony> Removing it completely might be better, it may force people to
Tony> look at how they are using HZ. But there are probably many old
Tony> programs that have:
After reading through the discussion that was what I kept coming back
to.
Tony> #ifndef HZ #define HZ 60 #endif
Tony> So this won't catch them.
Tony> The ultimate safe solution might be:
Tony> #define HZ Fix your program to use sysconf(_SC_CLK_TCK)! \ (and
Tony> BTW, you should not include kernel headers)
Tony> Which is highly likely to cause a compile failure (but should at
Tony> least provide a clue to the user on what they should do).
You have my vote for that one. Anything else is just going to cause
those broken userapps to continue doing the wrong thing. We should
really do this on all archs though.
Cheers,
Jes
next prev parent reply other threads:[~2006-06-29 9:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 17:36 [PATCH] ia64: change usermode HZ to 250 Luck, Tony
2006-06-29 9:37 ` Jes Sorensen [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-07-09 19:18 Luck, Tony
2006-06-29 14:09 Albert Cahalan
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-27 22:01 hawkes
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
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=yq04py4i9p7.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--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=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