From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Guillaume Chazarain <guichaz@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>, Frans Pop <elendil@planet.nl>,
Parag Warudkar <parag.warudkar@gmail.com>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: 'global' rq->clock (was Re: Horrendous Audio Stutter - current git)
Date: Fri, 02 May 2008 22:46:05 +0200 [thread overview]
Message-ID: <1209761165.6929.25.camel@lappy> (raw)
In-Reply-To: <3d8471ca0805021338x7cde7d1fwbbb58a6c65a1349d@mail.gmail.com>
On Fri, 2008-05-02 at 22:38 +0200, Guillaume Chazarain wrote:
> On Fri, May 2, 2008 at 9:56 PM, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> > Let me try and come up with something slightly less horrible
>
> Does this obsolete Ingo's "sched: make cpu_clock() globally synchronous"?
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=27ec4407790d075c325e1f4da0a19c56953cce23
>
> My laptop is UP, so I cannot test this :-(
It doesn't, I'm just throwing around code/ideas.
We should probably come up with some clock lib that builds the various
clocks: rq->clock and cpu_clock() from sched_clock() depending on some
architecture supplied hints.
We can toss most of this code on archs like power64, sparc64 and s390x
which have stable clocks. It just seems wrong to do all this on these
archs, but don't have much choice on x86.
next prev parent reply other threads:[~2008-05-02 20:46 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 0:14 Horrendous Audio Stutter - current git Parag Warudkar
2008-05-02 8:34 ` Peter Zijlstra
2008-05-02 10:32 ` Frans Pop
2008-05-02 10:35 ` Peter Zijlstra
2008-05-02 11:08 ` Peter Zijlstra
2008-05-02 11:37 ` Frans Pop
2008-05-02 11:39 ` Peter Zijlstra
2008-05-02 11:45 ` Frans Pop
2008-05-02 11:51 ` Peter Zijlstra
2008-05-02 12:06 ` Frans Pop
2008-05-02 12:22 ` Parag Warudkar
2008-05-02 13:21 ` Dhaval Giani
2008-05-02 11:10 ` Parag Warudkar
2008-05-02 12:09 ` Mike Galbraith
2008-05-02 12:21 ` Parag Warudkar
2008-05-02 12:37 ` Mike Galbraith
2008-05-02 15:02 ` Mike Galbraith
2008-05-02 15:49 ` Frans Pop
2008-05-02 18:53 ` Frans Pop
2008-05-02 19:27 ` Mike Galbraith
2008-05-02 19:56 ` 'global' rq->clock (was Re: Horrendous Audio Stutter - current git) Peter Zijlstra
2008-05-02 20:38 ` Guillaume Chazarain
2008-05-02 20:46 ` Peter Zijlstra [this message]
2008-05-02 22:00 ` 'global' rq->clock David Miller
2008-05-02 21:48 ` David Miller
2008-05-02 10:09 ` Arjan van de Ven
2008-05-04 12:12 ` Peter Zijlstra
2008-05-02 22:07 ` Peter Zijlstra
2008-05-03 8:28 ` Ingo Molnar
2008-05-03 9:05 ` David Miller
2008-05-03 10:10 ` Ingo Molnar
2008-05-03 19:27 ` David Miller
2008-05-03 19:37 ` Ingo Molnar
2008-05-03 22:30 ` Benjamin Herrenschmidt
2008-05-03 22:38 ` Ingo Molnar
2008-05-03 23:04 ` David Miller
2008-05-03 23:36 ` David Miller
2008-05-03 23:38 ` Ingo Molnar
2008-05-03 23:40 ` David Miller
2008-05-03 23:47 ` Ingo Molnar
2008-05-04 2:22 ` Benjamin Herrenschmidt
2008-05-03 19:28 ` David Miller
2008-05-03 19:39 ` Ingo Molnar
2008-05-03 6:20 ` 'global' rq->clock (was Re: Horrendous Audio Stutter - current git) Mike Galbraith
2008-05-02 19:38 ` Horrendous Audio Stutter - current git Mike Galbraith
2008-05-03 7:13 ` Frans Pop
2008-05-03 7:39 ` Mike Galbraith
2008-05-07 8:26 ` Frans Pop
2008-05-07 8:32 ` Ingo Molnar
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=1209761165.6929.25.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=efault@gmx.de \
--cc=elendil@planet.nl \
--cc=guichaz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=parag.warudkar@gmail.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