[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180212123430.6f8e4d6e@gandalf.local.home>
Date: Mon, 12 Feb 2018 12:34:30 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Juri Lelli <juri.lelli@...hat.com>
Cc: peterz@...radead.org, mingo@...hat.com,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
vincent.guittot@...aro.org, luca.abeni@...tannapisa.it,
claudio@...dence.eu.com, tommaso.cucinotta@...tannapisa.it,
bristot@...hat.com, mathieu.poirier@...aro.org, tkjos@...roid.com,
joelaf@...gle.com, morten.rasmussen@....com,
dietmar.eggemann@....com, patrick.bellasi@....com,
alessio.balsini@....com
Subject: Re: [RFC PATCH 1/3] sched/deadline: merge dl_bw into dl_bandwidth
On Mon, 12 Feb 2018 14:40:28 +0100
Juri Lelli <juri.lelli@...hat.com> wrote:
> + * - dl_bw (< 100%) is the bandwidth of the system (domain) on each CPU;
> + * - dl_total_bw array contains the currently allocated bandwidth on the
> + * i-eth CPU.
The comment for dl_total_bw doesn't make sense. You mean that
dl_total_bw is the cpu's bandwidth? If so, let's not call it total,
because that would suggest it's the bandwidth of all CPUs. What about
dl_cpu_bw?
-- Steve
Powered by blists - more mailing lists