From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] - sched_clock() broken for ia64 SN platform
Date: Thu, 20 Nov 2003 06:01:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106930814009175@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106928980122896@msgid-missing>
>>>>> On Wed, 19 Nov 2003 20:09:15 -0800, "John Hawkes" <hawkes@sgi.com> said:
John> I'd like to hear an argument about why sched_clock() needs
John> sub-microsecond accuracy, instead of just using jiffies, when
John> one use of sched_clock() is to compare a delta time against
John> cache_decay_ticks, which is a "jiffies"-granularity value, and
John> the other use is to determine the relative
John> computebound-vs-interactive characteristics of the process.
It's probably best to discuss this on lkml. I didn't follow all the
recent scheduler developments but AFAIK, this is largely driven by
trying to fix some scheduling corners. I think the "persistent
starvation" bug that Stephane found gets fixed by it, for example.
Also, supposedly it helps interactivity.
--david
next prev parent reply other threads:[~2003-11-20 6:01 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 [this message]
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
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-106930814009175@msgid-missing \
--to=davidm@napali.hpl.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.