[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181002131657.7lysubukna4tkjly@queper01-lin>
Date: Tue, 2 Oct 2018 14:16:59 +0100
From: Quentin Perret <quentin.perret@....com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: rjw@...ysocki.net, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, gregkh@...uxfoundation.org,
mingo@...hat.com, dietmar.eggemann@....com,
morten.rasmussen@....com, chris.redpath@....com,
patrick.bellasi@....com, valentin.schneider@....com,
vincent.guittot@...aro.org, thara.gopinath@...aro.org,
viresh.kumar@...aro.org, tkjos@...gle.com, joel@...lfernandes.org,
smuckle@...gle.com, adharmap@...eaurora.org,
skannan@...eaurora.org, pkondeti@...eaurora.org,
juri.lelli@...hat.com, edubezval@...il.com,
srinivas.pandruvada@...ux.intel.com, currojerez@...eup.net,
javi.merino@...nel.org
Subject: Re: [PATCH v7 06/14] sched/topology: Reference the Energy Model of
CPUs when available
On Tuesday 02 Oct 2018 at 14:36:17 (+0200), Peter Zijlstra wrote:
> On Wed, Sep 12, 2018 at 10:13:01AM +0100, Quentin Perret wrote:
> > +struct perf_domain {
> > + struct em_perf_domain *obj;
> > + struct perf_domain *next;
> > + struct rcu_head rcu;
> > +};
>
> Maybe s/obj/em_pd/ or something like that? @obj is so very opaque.
I wanted to avoid calling it just 'pd' since that could be confusing. So
anything different than that is fine by me. I don't have a better
suggestion than 'em_pd', so I'd say let's stick with that for now.
Thanks,
Quentin
Powered by blists - more mailing lists