On Wed, Feb 03, 2016 at 01:32:46PM +, Mel Gorman wrote:
> > Yes, but the question is, are there true cross-CPU cache-misses? I.e. are
> > there
> > any 'global' (or per node) counters that we keep touching and which keep
> > generating cache-misses?
> >
>
> I haven't specifically
On Wed, Feb 03, 2016 at 01:49:21PM +0100, Ingo Molnar wrote:
>
> * Mel Gorman wrote:
>
> > On Wed, Feb 03, 2016 at 12:28:49PM +0100, Ingo Molnar wrote:
> > >
> > > * Mel Gorman wrote:
> > >
> > > > Changelog since v3
> > > > o Force enable stats during profiling and latencytop
> > > >
> > >
* Mel Gorman wrote:
> On Wed, Feb 03, 2016 at 12:28:49PM +0100, Ingo Molnar wrote:
> >
> > * Mel Gorman wrote:
> >
> > > Changelog since v3
> > > o Force enable stats during profiling and latencytop
> > >
> > > Changelog since V2
> > > o Print stats that are not related to schedstat
> > > o
> Changelog since v3
> o Force enable stats during profiling and latencytop
>
> Changelog since V2
> o Print stats that are not related to schedstat
> o Reintroduce a static inline for update_stats_dequeue
>
> Changelog since V1
> o Introduce schedstat_enabled and address Ingo's feedback
> o
On Wed, Feb 03, 2016 at 12:28:49PM +0100, Ingo Molnar wrote:
>
> * Mel Gorman wrote:
>
> > Changelog since v3
> > o Force enable stats during profiling and latencytop
> >
> > Changelog since V2
> > o Print stats that are not related to schedstat
> > o Reintroduce a static inline for
* Mel Gorman wrote:
> Changelog since v3
> o Force enable stats during profiling and latencytop
>
> Changelog since V2
> o Print stats that are not related to schedstat
> o Reintroduce a static inline for update_stats_dequeue
>
> Changelog since V1
> o Introduce schedstat_enabled and address
Changelog since v3
o Force enable stats during profiling and latencytop
Changelog since V2
o Print stats that are not related to schedstat
o Reintroduce a static inline for update_stats_dequeue
Changelog since V1
o Introduce schedstat_enabled and address Ingo's feedback
o More schedstat-only
* Mel Gorman wrote:
> Changelog since v3
> o Force enable stats during profiling and latencytop
>
> Changelog since V2
> o Print stats that are not related to schedstat
> o Reintroduce a static inline for update_stats_dequeue
>
> Changelog since V1
> o Introduce
On Wed, Feb 03, 2016 at 01:49:21PM +0100, Ingo Molnar wrote:
>
> * Mel Gorman wrote:
>
> > On Wed, Feb 03, 2016 at 12:28:49PM +0100, Ingo Molnar wrote:
> > >
> > > * Mel Gorman wrote:
> > >
> > > > Changelog since v3
> > > > o Force
> Changelog since v3
> o Force enable stats during profiling and latencytop
>
> Changelog since V2
> o Print stats that are not related to schedstat
> o Reintroduce a static inline for update_stats_dequeue
>
> Changelog since V1
> o Introduce schedstat_enabled and address Ingo's feedback
> o
On Wed, Feb 03, 2016 at 12:28:49PM +0100, Ingo Molnar wrote:
>
> * Mel Gorman wrote:
>
> > Changelog since v3
> > o Force enable stats during profiling and latencytop
> >
> > Changelog since V2
> > o Print stats that are not related to schedstat
> > o Reintroduce a
Changelog since v3
o Force enable stats during profiling and latencytop
Changelog since V2
o Print stats that are not related to schedstat
o Reintroduce a static inline for update_stats_dequeue
Changelog since V1
o Introduce schedstat_enabled and address Ingo's feedback
o More schedstat-only
On Wed, Feb 03, 2016 at 01:32:46PM +, Mel Gorman wrote:
> > Yes, but the question is, are there true cross-CPU cache-misses? I.e. are
> > there
> > any 'global' (or per node) counters that we keep touching and which keep
> > generating cache-misses?
> >
>
> I haven't specifically
* Mel Gorman wrote:
> On Wed, Feb 03, 2016 at 12:28:49PM +0100, Ingo Molnar wrote:
> >
> > * Mel Gorman wrote:
> >
> > > Changelog since v3
> > > o Force enable stats during profiling and latencytop
> > >
> > > Changelog since V2
> >
14 matches
Mail list logo