From: john stultz <johnstul@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] - sched_clock() broken for ia64 SN platform
Date: Thu, 20 Nov 2003 21:58:34 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106936601610014@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106928980122896@msgid-missing>
On Thu, 2003-11-20 at 13:27, David Mosberger wrote:
> >>>>> On Thu, 20 Nov 2003 12:58:20 -0800, "John Hawkes" <hawkes@sgi.com> said:
>
> John> I doubt this double-count would ever be accepted by the wider
> John> Linux Community, as it bloats mainline arch-independent code,
> John> just to fix a problem with a handful of drifty platforms.
>
> That's not an argument: the "bloat" can be trivially hidden for
> non-drifty architectures with an inline routine or macro. I for one
> would be perfectly happy to pay an extra word in the ia64-version of
> task_struct if that would yield a generic and scalable solution to the
> problem. The problem right now is that the generic kernel code is
> structured in a way that prevents this.
I too was confused why per-cpu start and stop times were not just used
for this high-res accounting. I'm not sure I can look into it now, but
I'd be interested to hear why we'd compare timestamps across cpus
(rather then just use time deltas calculated on a single cpu).
Oh, and that last thought, keep it around for when 2.7 opens ;)
-john
next prev parent reply other threads:[~2003-11-20 21:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 0:56 [PATCH] - sched_clock() broken for ia64 SN platform John Hawkes
2003-11-20 1:24 ` David Mosberger
2003-11-20 4:09 ` John Hawkes
2003-11-20 6:01 ` David Mosberger
2003-11-20 15:23 ` Jack Steiner
2003-11-20 17:25 ` Grant Grundler
2003-11-20 17:25 ` Rich Altmaier
2003-11-20 18:32 ` David Mosberger
2003-11-20 19:20 ` Robin Holt
2003-11-20 19:23 ` Robin Holt
2003-11-20 20:58 ` John Hawkes
2003-11-20 21:27 ` David Mosberger
2003-11-20 21:58 ` john stultz [this message]
2003-11-20 22:14 ` John Hawkes
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=marc-linux-ia64-106936601610014@msgid-missing \
--to=johnstul@us.ibm.com \
--cc=linux-ia64@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.