On Fri, 2005-11-18 at 17:25 -0500, Steven Rostedt wrote:
> On Fri, 18 Nov 2005, Lee Revell wrote:
>
> > On Fri, 2005-11-18 at 23:07 +0100, Ingo Molnar wrote:
> > > * Fernando Lopez-Lezcano <[email protected]> wrote:
> > >
> > > > Arghhh, at least I take this as a confirmation that the TSCs do drift
> > > > and there is no workaround. It currently makes the -rt/Jack
> > > > combination not very useful, at least in my tests.
> > > >
> > > > Is there a way to resync the TSCs?
> > >
> > > no reasonable way. Does idle=poll make any difference?
> >
> > But JACK itself uses rdtsc() for timing calculations so TSC drift is
> > invariably fatal.
>
> Can it simply be pinned to a cpu?
Is there a way to know in which cpu a process is running? At least Jack
could ignore timinig issues if the measurement is going to happen in a
different cpu than the one where the original timestamp was collected.
-- Fernando
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
