Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1610389

Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking trace event

From Peter Zijlstra <peterz@infradead.org>
Newsgroups linux.kernel
Subject Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking trace event
Date 2017-03-28 10:00 +0200
Message-ID <tpUcO-4ow-15@gated-at.bofh.it> (permalink)
References <tpSXo-3CJ-11@gated-at.bofh.it> <tpSXo-3CJ-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On Tue, Mar 28, 2017 at 07:35:38AM +0100, Dietmar Eggemann wrote:
> The trace event keys load and util (utilization) are mapped to:
> 
>  (1) load : cfs_rq->runnable_load_avg
> 
>  (2) util : cfs_rq->avg.util_avg
> 
> To let this trace event work for configurations w/ and w/o group
> scheduling support for cfs (CONFIG_FAIR_GROUP_SCHED) the following
> special handling is necessary for non-existent key=value pairs:
> 
>  path = "(null)" : In case of !CONFIG_FAIR_GROUP_SCHED.
> 
>  id   = -1       : In case of !CONFIG_FAIR_GROUP_SCHED.
> 
> The following list shows examples of the key=value pairs in different
> configurations for:
> 
>  (1) a root task_group:
> 
>      cpu=4 path=/ id=1 load=6 util=331

What's @id and why do we care?

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking trace event Dietmar Eggemann <dietmar.eggemann@arm.com> - 2017-03-28 08:40 +0200
  Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Peter Zijlstra <peterz@infradead.org> - 2017-03-28 10:00 +0200
    Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Dietmar Eggemann <dietmar.eggemann@arm.com> - 2017-03-28 15:40 +0200
  Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Peter Zijlstra <peterz@infradead.org> - 2017-03-28 10:10 +0200
    Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Steven Rostedt <rostedt@goodmis.org> - 2017-03-28 16:50 +0200
  Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Steven Rostedt <rostedt@goodmis.org> - 2017-03-28 16:50 +0200
    Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Peter Zijlstra <peterz@infradead.org> - 2017-03-28 18:50 +0200
      Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Peter Zijlstra <peterz@infradead.org> - 2017-03-28 19:10 +0200
        Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Patrick Bellasi <patrick.bellasi@arm.com> - 2017-03-28 19:30 +0200
          Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Peter Zijlstra <peterz@infradead.org> - 2017-03-28 20:20 +0200
      Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Steven Rostedt <rostedt@goodmis.org> - 2017-03-28 19:50 +0200
        Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Steven Rostedt <rostedt@goodmis.org> - 2017-03-28 19:50 +0200
          Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Dietmar Eggemann <dietmar.eggemann@arm.com> - 2017-03-29 22:50 +0200
      Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Dietmar Eggemann <dietmar.eggemann@arm.com> - 2017-03-29 23:10 +0200
        Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Peter Zijlstra <peterz@infradead.org> - 2017-03-30 09:10 +0200
          Re: [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking  trace event Dietmar Eggemann <dietmar.eggemann@arm.com> - 2017-03-30 09:50 +0200

csiph-web