From: "Tony Luck" <tony.luck@intel.com>
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>,
John Daiker <jdaiker@osdl.org>, John Hawkes <hawkes@sgi.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: Sat, 08 Jul 2006 02:51:52 +0000 [thread overview]
Message-ID: <12c511ca0607071951p4fe7e1bfm7be5ad48ede895f1@mail.gmail.com> (raw)
In-Reply-To: <20060708001427.GA723842@sgi.com>
> So does i386 convert the return value of the times(2) call to user
> hertz? On IA64, it returns the value in internal clock ticks, and
> then when a program uses the value in param.h, it gets it wrong now,
> because internal HZ is now 250.
>
> So is times() is broken in IA64, or is this an exception to Alan's
> statement?
The Linux man page for times(2) specifically says "ticks" and refers
to sysconf for how to determine how long a "tick" is. So ia64 matches
the man page. Dunno if that matches POSIX though.
-Tony
next prev parent reply other threads:[~2006-07-08 2:51 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 [this message]
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
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=12c511ca0607071951p4fe7e1bfm7be5ad48ede895f1@mail.gmail.com \
--to=tony.luck@intel.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=jes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.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