From: Nick Piggin <piggin@cyberone.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH] 2.6.0-test11 sched_clock() broken for "drifty ITC"
Date: Sat, 20 Dec 2003 15:12:45 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107193415625580@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107178053026093@msgid-missing>
Andrew Morton wrote:
>Nick Piggin <piggin@cyberone.com.au> wrote:
>
>>
>>
>>Ingo Molnar wrote:
>>
>>
>>>So i believe the generic relaxing of sched_clock() synchronization is
>>>the right thing to do. I like your patch. It adds minimal overhead and
>>>solves a hard problem - nice work! Andrew, please apply it.
>>>
>>>
>>>
>>Its a great looking patch if you must have high res sched_clock. So
>>I guess I agree with it.
>>
>
>miaow ;)
>
I'm just thinking that computers with unsynched clocks have less
need for good interactivity, but thats probably too narrow and x86
a view anyway.
>
>>Can we have a scheduler day when Andrew is ready to take patches for
>>it? I have a few small changes that I'd like to get merged soon too
>>(not sched domains - that should probably go to the mm tree for a while)
>>
>>Relevant patches are
>>sched-ctx-count-preempt.patch
>>sched-fork-cleanup.patch
>>sched-migrate-comment.patch
>>sched-style.patch
>>sched-migrate-affinity-race.patch
>>
>>
>
>Post 'em.
>
OK, I'll trim the cc list though...
next prev parent reply other threads:[~2003-12-20 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 20:44 [RFC][PATCH] 2.6.0-test11 sched_clock() broken for "drifty ITC" John Hawkes
2003-12-18 22:37 ` john stultz
2003-12-20 10:41 ` Andrew Morton
2003-12-20 10:50 ` Ingo Molnar
2003-12-20 14:57 ` Nick Piggin
2003-12-20 15:05 ` Andrew Morton
2003-12-20 15:12 ` Nick Piggin [this message]
2003-12-20 16:36 ` Ingo Molnar
2003-12-20 21:41 ` Zwane Mwaikambo
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-107193415625580@msgid-missing \
--to=piggin@cyberone.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox