From: Tejun Heo <tj@kernel.org>
To: Josh Don <joshdon@google.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Cruz Zhao <CruzZhao@linux.alibaba.com>
Subject: Re: [PATCH v3] sched/core: add forced idle accounting for cgroups
Date: Wed, 29 Jun 2022 02:57:17 +0900 [thread overview]
Message-ID: <YrtA/ZksAYaxqcx3@mtj.duckdns.org> (raw)
In-Reply-To: <CABk29NvMRWbJgZ7VdzdeDVz0v=PKJJJ0gFk=+X884U25ZJhbsA@mail.gmail.com>
Hello,
On Mon, Jun 27, 2022 at 03:35:21PM -0700, Josh Don wrote:
> > Would it make sense to namespace the name to reflect the fact that
> > this is tied to core scheduling? e.g. something like
> > core.force_idle_usec (and yeah, underscore between words, please). I
> > kinda hate that the feature is named "core". The word is so
> > overloaded.
>
> Sure, although a namespace of "core_sched" would be a bit clearer,
> since as you point out "core" is pretty overloaded :)
Yeah, core_sched is probabaly better and hopefully it'll get better as
we get used to the name.
> Lack of underscore for forceidle was to be consistent with
> "core_forceidle_sum" being dumped from /proc/pid/sched, but I'm fine
> with it either way.
>
> So,
>
> core_sched.force_idle_usec ?
Yeah, that'd be my preference.
Thanks.
--
tejun
prev parent reply other threads:[~2022-06-28 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 23:44 Josh Don
2022-06-27 9:15 ` Tejun Heo
2022-06-27 22:35 ` Josh Don
2022-06-28 17:57 ` Tejun Heo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YrtA/ZksAYaxqcx3@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=CruzZhao@linux.alibaba.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=joshdon@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®