From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] - sched_clock() broken for ia64 SN platform
Date: Thu, 20 Nov 2003 17:25:45 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106934978321459@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106928980122896@msgid-missing>
On Wed, Nov 19, 2003 at 08:09:15PM -0800, John Hawkes wrote:
> I'd like to hear an argument about why sched_clock() needs sub-microsecond
> accuracy, instead of just using jiffies, when one use of sched_clock() is to
> compare a delta time against cache_decay_ticks, which is a
> "jiffies"-granularity value, and the other use is to determine the relative
> computebound-vs-interactive characteristics of the process.
In general, it seems like bouncing the jiffies cacheline around is more of
a problem than the need for accuracy. This sounds like a similar problem
Jack Steiner wrote about before (updating interrupt counts):
| Updating the counter causes a cache line to be bounced between
| cpus at a rate of at least HZ*active_cpus. (The number of bus transactions
| is at least 2X higher because the line is first obtained for
| shared usage, then upgraded to modified. In addition, multiple references
| are made to the line for each interrupt. On a big system, it is unlikely that
| a cpu can hold the line for entire time that the interrupt is being
| serviced).
hth,
grant
next prev parent reply other threads:[~2003-11-20 17:25 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 [this message]
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
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-106934978321459@msgid-missing \
--to=iod00d@hp.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.