On Mon, 2005-05-16 at 13:58 -0700, David Mosberger wrote: > >>>>> On Mon, 16 May 2005 13:53:44 -0700, john stultz <[email protected]> said: > John> You've only pointed out two timesources that could want this > John> (ITC and TSC), so I think its reasonable to do your jitter > John> handling in the timesource driver. If there are other arches > John> that have non hardware synced per-cpu counters, then it would > John> be something to consider. > > I think Christopher's point is that _all_ time-sources which require > software syncing will need this since it is not possible to sync > perfectly, even if there is no drift. Yes, but to my knowledge it is only the ITC that does software syncing. The TSC could use it as well, but doesn't. Other then that I haven't heard of any other timesource that would use such functionality. Since its possible to do jitter compensation within the itc timesource driver (and within the fastcall code to preserve the existing performance), would it be reasonable to deffer making the jitter compensation code generic until another timesource needs it? It should be a fairly simple change. Or is this just something I'm being hard-headed about? thanks -john - 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: IA64 implementation of timesource for new time of day subsystem
- From: Christoph Lameter <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- References:
- [RFC][PATCH (1/7)] new timeofday subsystem (v A5)
- From: john stultz <[email protected]>
- [RFC][PATCH (2/7)] new timeofday i386 arch specific changes (v A5)
- From: john stultz <[email protected]>
- [RFC][PATCH (3/7)] new timeofday x86-64 specific changes (v A5)
- From: john stultz <[email protected]>
- [RFC][PATCH (4/7)] new timeofday i386 and x86-64 timesources (v A5)
- From: john stultz <[email protected]>
- [RFC][PATCH (5/7)] new timeofday ia64,ppc32,ppc64 and s390 arch specific hooks (v A5)
- From: john stultz <[email protected]>
- IA64 implementation of timesource for new time of day subsystem
- From: Christoph Lameter <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: john stultz <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: Christoph Lameter <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: john stultz <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: Christoph Lameter <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: David Mosberger <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: john stultz <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: Christoph Lameter <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: john stultz <[email protected]>
- Re: IA64 implementation of timesource for new time of day subsystem
- From: David Mosberger <[email protected]>
- [RFC][PATCH (1/7)] new timeofday subsystem (v A5)
- Prev by Date: Re: How to use memory over 4GB
- Next by Date: Re: [PATCH 7/8] ppc64: SPU file system
- Previous by thread: Re: IA64 implementation of timesource for new time of day subsystem
- Next by thread: Re: IA64 implementation of timesource for new time of day subsystem
- Index(es):