Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-26 Thread Nicolai Stange
Nicolai Stange writes: > Thomas Gleixner writes: > >> On Wed, 21 Sep 2016, Nicolai Stange wrote: >>> Thomas Gleixner writes: >>> >>> > On Wed, 21 Sep 2016, Nicolai Stange wrote: >>> >> Thomas Gleixner writes:

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-26 Thread Nicolai Stange
Nicolai Stange writes: > Thomas Gleixner writes: > >> On Wed, 21 Sep 2016, Nicolai Stange wrote: >>> Thomas Gleixner writes: >>> >>> > On Wed, 21 Sep 2016, Nicolai Stange wrote: >>> >> Thomas Gleixner writes: >>> >> > Have you ever measured the overhead of the extra work which has to be >>>

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-22 Thread Nicolai Stange
Thomas Gleixner writes: > On Wed, 21 Sep 2016, Nicolai Stange wrote: >> Thomas Gleixner writes: >> >> > On Wed, 21 Sep 2016, Nicolai Stange wrote: >> >> Thomas Gleixner writes: >> >> > Have you ever measured the overhead of the extra

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-22 Thread Nicolai Stange
Thomas Gleixner writes: > On Wed, 21 Sep 2016, Nicolai Stange wrote: >> Thomas Gleixner writes: >> >> > On Wed, 21 Sep 2016, Nicolai Stange wrote: >> >> Thomas Gleixner writes: >> >> > Have you ever measured the overhead of the extra work which has to be >> >> > done >> >> > in

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-22 Thread Thomas Gleixner
On Wed, 21 Sep 2016, Nicolai Stange wrote: > Thomas Gleixner writes: > > > On Wed, 21 Sep 2016, Nicolai Stange wrote: > >> Thomas Gleixner writes: > >> > Have you ever measured the overhead of the extra work which has to be > >> > done > >> > in

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-22 Thread Thomas Gleixner
On Wed, 21 Sep 2016, Nicolai Stange wrote: > Thomas Gleixner writes: > > > On Wed, 21 Sep 2016, Nicolai Stange wrote: > >> Thomas Gleixner writes: > >> > Have you ever measured the overhead of the extra work which has to be > >> > done > >> > in clockevents_adjust_all_freqs() ? > >> > >> Not

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-21 Thread Nicolai Stange
Thomas Gleixner writes: > On Wed, 21 Sep 2016, Nicolai Stange wrote: >> Thomas Gleixner writes: >> > Have you ever measured the overhead of the extra work which has to be done >> > in clockevents_adjust_all_freqs() ? >> >> Not exactly, I had a look at

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-21 Thread Nicolai Stange
Thomas Gleixner writes: > On Wed, 21 Sep 2016, Nicolai Stange wrote: >> Thomas Gleixner writes: >> > Have you ever measured the overhead of the extra work which has to be done >> > in clockevents_adjust_all_freqs() ? >> >> Not exactly, I had a look at its invocation frequency which seems to >>

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-20 Thread Thomas Gleixner
On Wed, 21 Sep 2016, Nicolai Stange wrote: > Thomas Gleixner writes: > > Have you ever measured the overhead of the extra work which has to be done > > in clockevents_adjust_all_freqs() ? > > Not exactly, I had a look at its invocation frequency which seems to > decay

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-20 Thread Thomas Gleixner
On Wed, 21 Sep 2016, Nicolai Stange wrote: > Thomas Gleixner writes: > > Have you ever measured the overhead of the extra work which has to be done > > in clockevents_adjust_all_freqs() ? > > Not exactly, I had a look at its invocation frequency which seems to > decay exponentially with uptime,

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-20 Thread Nicolai Stange
Thomas Gleixner writes: > On Fri, 16 Sep 2016, Nicolai Stange wrote: > >> Goal: avoid programming ced devices too early for large deltas, for >> details, c.f. the description of [21/23]. >> >> [21-23/23] Actually do the frequency adjustments. >> >> Tested on x86_64

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-20 Thread Nicolai Stange
Thomas Gleixner writes: > On Fri, 16 Sep 2016, Nicolai Stange wrote: > >> Goal: avoid programming ced devices too early for large deltas, for >> details, c.f. the description of [21/23]. >> >> [21-23/23] Actually do the frequency adjustments. >> >> Tested on x86_64 and next-20160916. > >

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-20 Thread Thomas Gleixner
On Fri, 16 Sep 2016, Nicolai Stange wrote: > Goal: avoid programming ced devices too early for large deltas, for > details, c.f. the description of [21/23]. > > [21-23/23] Actually do the frequency adjustments. > > Tested on x86_64 and next-20160916. Have you ever measured the overhead

Re: [RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-20 Thread Thomas Gleixner
On Fri, 16 Sep 2016, Nicolai Stange wrote: > Goal: avoid programming ced devices too early for large deltas, for > details, c.f. the description of [21/23]. > > [21-23/23] Actually do the frequency adjustments. > > Tested on x86_64 and next-20160916. Have you ever measured the overhead

[RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-16 Thread Nicolai Stange
Goal: avoid programming ced devices too early for large deltas, for details, c.f. the description of [21/23]. Previous v6 can be found here: http://lkml.kernel.org/r/20160909200033.32103-1-nicsta...@gmail.com Your objections [0] to v6 have both been towards [1/23] ("clocksource: sh_cmt:

[RFC v7 00/23] adapt clockevents frequencies to mono clock

2016-09-16 Thread Nicolai Stange
Goal: avoid programming ced devices too early for large deltas, for details, c.f. the description of [21/23]. Previous v6 can be found here: http://lkml.kernel.org/r/20160909200033.32103-1-nicsta...@gmail.com Your objections [0] to v6 have both been towards [1/23] ("clocksource: sh_cmt: