Gilles Chanteperdrix wrote:
> Gilles Chanteperdrix wrote:
> > Jan Kiszka wrote:
> > > Gilles Chanteperdrix wrote:
> > > > Jan Kiszka wrote:
> > > > > Gilles Chanteperdrix wrote:
> > > > > > Jan Kiszka wrote:
> > > > > > > Gilles Chanteperdrix wrote:
> > > > > > > > Hi,
> > > >
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
> > Gilles Chanteperdrix wrote:
> > > Jan Kiszka wrote:
> > > > Gilles Chanteperdrix wrote:
> > > > > Jan Kiszka wrote:
> > > > > > Gilles Chanteperdrix wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > here comes, for r
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
> > Jan Kiszka wrote:
> > > Gilles Chanteperdrix wrote:
> > > > Jan Kiszka wrote:
> > > > > Gilles Chanteperdrix wrote:
> > > > > > Hi,
> > > > > >
> > > > > > here comes, for review, a patch which reduces the overhead of
> > > >
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
> > Gilles Chanteperdrix wrote:
> > > Jan Kiszka wrote:
> > > > Gilles Chanteperdrix wrote:
> > > > > Hi,
> > > > >
> > > > > here comes, for review, a patch which reduces the overhead of
> > > > > clock_gettime by directly reading the ts
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
> > Jan Kiszka wrote:
> > > Gilles Chanteperdrix wrote:
> > > > Hi,
> > > >
> > > > here comes, for review, a patch which reduces the overhead of
> > > > clock_gettime by directly reading the tsc in user-space for
> > > > architectures
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
> > Gilles Chanteperdrix wrote:
> > > Hi,
> > >
> > > here comes, for review, a patch which reduces the overhead of
> > > clock_gettime by directly reading the tsc in user-space for
> > > architectures that support it.
> >
> > Highly welcome
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
> > Hi,
> >
> > here comes, for review, a patch which reduces the overhead of
> > clock_gettime by directly reading the tsc in user-space for
> > architectures that support it.
>
> Highly welcome. But I have one concern: How and when do you
Gilles Chanteperdrix wrote:
> Hi,
>
> here comes, for review, a patch which reduces the overhead of
> clock_gettime by directly reading the tsc in user-space for
> architectures that support it.
Highly welcome. But I have one concern: How and when do you propagate
wallclock_offset changes to user