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: Mon, 10 Jul 2006 21:01:53 -0600 [thread overview]
Message-ID: <ed5aea430607102001g514bfa97jf82c25a038e9c436@mail.gmail.com> (raw)
In-Reply-To: <20060710202228.GA732959@sgi.com>
On 7/10/06, Jeremy Higdon <jeremy@sgi.com> wrote:
> On Sat, Jul 08, 2006 at 07:07:14AM -0600, David Mosberger-Tang wrote:
> > Nothing is broken. Read Alan's statement carefully...
> >
> > --david
>
> His statement can be read a couple of ways.
Alan said:
--------------------------------------------------------------
From: Alan Cox <alan_at_lxorguk.ukuu.org.uk>
Date: 2006-06-29 21:02:08
Ar Iau, 2006-06-29 am 05:37 -0400, ysgrifennodd Jes Sorensen:
> 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.
No need, all current mainstream architectures expose a constant user HZ.
Alan
--------------------------------------------------------------
Note that Alan didn't claim that *all* (Linux-supported) architectures
expose a constant user HZ, only the "mainstream" ones. I won't get
into the debate as to what qualifies as "mainstream", but clearly IA64
does not (and should not) expose a constant value, since there were no
legacy-binary-issue and we chose to insist that apps should uses
sysconf() or equivalent if they need to know the clocktick.
--david
--
Mosberger Consulting LLC, http://www.mosberger-consulting.com/
next prev parent reply other threads:[~2006-07-11 3:02 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
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 [this message]
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=ed5aea430607102001g514bfa97jf82c25a038e9c436@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