From: Benjamin Segall <bsegall@google.com>
To: Li kunyu <kunyu@nfschina.com>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, mgorman@suse.de, bristot@redhat.com,
vschneid@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: core: Optimize the structure of 'tg_cfs_schedulable_down' function
Date: Mon, 20 Mar 2023 15:48:36 -0700 [thread overview]
Message-ID: <xm26o7onvy2j.fsf@google.com> (raw)
In-Reply-To: <20230319200255.3640-1-kunyu@nfschina.com> (Li kunyu's message of "Mon, 20 Mar 2023 04:02:55 +0800")
Li kunyu <kunyu@nfschina.com> writes:
> Optimize if branches and define in the branch statement
> block parent_quota variable.
It's not an optimization; it is arguably a slight style improvement.
>
> Signed-off-by: Li kunyu <kunyu@nfschina.com>
> ---
> kernel/sched/core.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 488655f2319f..7e8535d2e36d 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -10915,15 +10915,12 @@ static int tg_cfs_schedulable_down(struct task_group *tg, void *data)
> {
> struct cfs_schedulable_data *d = data;
> struct cfs_bandwidth *cfs_b = &tg->cfs_bandwidth;
> - s64 quota = 0, parent_quota = -1;
> + s64 quota = RUNTIME_INF;
>
> - if (!tg->parent) {
> - quota = RUNTIME_INF;
> - } else {
> + if (tg->parent) {
> struct cfs_bandwidth *parent_b = &tg->parent->cfs_bandwidth;
> -
> + s64 parent_quota = parent_b->hierarchical_quota;
> quota = normalize_cfs_quota(tg, d);
> - parent_quota = parent_b->hierarchical_quota;
>
> /*
> * Ensure max(child_quota) <= parent_quota. On cgroup2,
prev parent reply other threads:[~2023-03-20 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 20:02 [PATCH] sched: core: Optimize the structure of 'tg_cfs_schedulable_down' function Li kunyu
2023-03-20 22:48 ` Benjamin Segall [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=xm26o7onvy2j.fsf@google.com \
--to=bsegall@google.com \
--cc=bristot@redhat.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kunyu@nfschina.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