From: "Li,Rongqing" <lirongqing@baidu.com>
To: "mingo@redhat.com" <mingo@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"juri.lelli@redhat.com" <juri.lelli@redhat.com>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 答复: [PATCH] sched/core: return prio_less() directly in __sched_core_less
Date: Fri, 22 Oct 2021 04:17:33 +0000 [thread overview]
Message-ID: <720137bdc33749a49b00ecb412d954da@baidu.com> (raw)
In-Reply-To: <1629800356-45550-1-git-send-email-lirongqing@baidu.com>
Ping
-Li
> -----邮件原件-----
> 发件人: Li,Rongqing <lirongqing@baidu.com>
> 发送时间: 2021年8月24日 18:19
> 收件人: mingo@redhat.com; peterz@infradead.org; juri.lelli@redhat.com;
> vincent.guittot@linaro.org; linux-kernel@vger.kernel.org; Li,Rongqing
> <lirongqing@baidu.com>
> 主题: [PATCH] sched/core: return prio_less() directly in __sched_core_less
>
> return prio_less() directly to avoid unnecessary checking
>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
> kernel/sched/core.c | 5 +----
> 1 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 2d9ff40..73478c9
> 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -140,10 +140,7 @@ static inline bool __sched_core_less(struct task_struct
> *a, struct task_struct *
> return false;
>
> /* flip prio, so high prio is leftmost */
> - if (prio_less(b, a, task_rq(a)->core->core_forceidle))
> - return true;
> -
> - return false;
> + return prio_less(b, a, task_rq(a)->core->core_forceidle);
> }
>
> #define __node_2_sc(node) rb_entry((node), struct task_struct, core_node)
> --
> 1.7.1
prev parent reply other threads:[~2021-10-22 4:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 10:19 [PATCH] sched/core: return prio_less() directly in __sched_core_less Li RongQing
2021-09-27 13:08 ` 答复: " Li,Rongqing
2021-10-22 4:17 ` Li,Rongqing [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=720137bdc33749a49b00ecb412d954da@baidu.com \
--to=lirongqing@baidu.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
/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