From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: akpm@osdl.org, johnstul@us.ibm.com, mingo@elte.hu,
zippel@linux-m68k.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: + clocksource-increase-initcall-priority.patch added to -mm tree
Date: Sun, 08 Oct 2006 23:38:25 +0200 [thread overview]
Message-ID: <1160343506.5686.113.camel@localhost.localdomain> (raw)
In-Reply-To: <1160343099.3693.153.camel@c-67-180-230-165.hsd1.ca.comcast.net>
On Sun, 2006-10-08 at 14:31 -0700, Daniel Walker wrote:
> On Sun, 2006-10-08 at 23:20 +0200, Thomas Gleixner wrote:
> > On Sun, 2006-10-08 at 14:15 -0700, Daniel Walker wrote:
> > > >
> > > > Which one exactly? I'm not aware of a problem with the existing code at
> > > > all.
> > >
> > > Clock shuffling.
> >
> > What's the problem with that ? It replaces clocks. Where _is_ the
> > problem ?
>
> The problem is that it's not optimal to have clocks switching furiously.
> This is something John notes as an issue in the unchanged
> kernel/time/clocksource.c file.
I don't see that behaviour on my machines and nobody complains about
that. I don't care about stale comments. Point me to a bug report
instead of your perception of what's optimal and not.
Working is not necessary optimal, but your vision of optimal is not
necessarily working either.
tglx
next prev parent reply other threads:[~2006-10-08 21:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610070153.k971ren4020838@shell0.pdx.osdl.net>
2006-10-08 8:06 ` + clocksource-increase-initcall-priority.patch added to -mm tree Thomas Gleixner
2006-10-08 10:19 ` Thomas Gleixner
2006-10-08 14:50 ` Daniel Walker
2006-10-08 14:53 ` Thomas Gleixner
2006-10-08 15:45 ` Daniel Walker
2006-10-08 15:58 ` Thomas Gleixner
2006-10-08 16:18 ` Daniel Walker
2006-10-08 16:52 ` Thomas Gleixner
2006-10-08 17:17 ` Daniel Walker
2006-10-08 19:03 ` Thomas Gleixner
2006-10-08 20:39 ` Daniel Walker
2006-10-08 20:52 ` Thomas Gleixner
2006-10-08 21:15 ` Daniel Walker
2006-10-08 21:20 ` Thomas Gleixner
2006-10-08 21:31 ` Daniel Walker
2006-10-08 21:38 ` Thomas Gleixner [this message]
2006-10-08 22:13 ` Daniel Walker
2006-10-08 22:53 ` Thomas Gleixner
2006-10-08 23:35 ` Daniel Walker
2006-10-09 6:56 ` Thomas Gleixner
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=1160343506.5686.113.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=dwalker@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zippel@linux-m68k.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.