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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- References:
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Thomas Gleixner <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- From: Daniel Walker <[email protected]>
- Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- Prev by Date: Re: [PATCH 2.6.19-rc1 V9] drivers: add LCD support
- Next by Date: Re: + clocksource-add-generic-sched_clock.patch added to -mm tree
- Previous by thread: Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- Next by thread: Re: + clocksource-increase-initcall-priority.patch added to -mm tree
- Index(es):