From: Hao Jia <jiahao.kernel@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>,
Hao Jia <jiahao1@lixiang.com>,
kernel-janitors@vger.kernel.org, Ben Segall <bsegall@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@kernel.org>,
Juri Lelli <juri.lelli@redhat.com>, Mel Gorman <mgorman@suse.de>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Valentin Schneider <vschneid@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v2] sched/core: Prioritize migrating eligible tasks in sched_balance_rq()
Date: Tue, 24 Dec 2024 09:53:48 +0800 [thread overview]
Message-ID: <2cfea522-8015-d86b-f78d-a6a2c56ba8b8@gmail.com> (raw)
In-Reply-To: <d983b931-b623-4af4-ac87-3807a86d1f87@web.de>
On 2024/12/24 04:50, Markus Elfring wrote:
> …
>> All of the benchmarks are done inside a normal cpu cgroup in a
>> clean environment with cpu turbo disabled, and test machine is:
> …
> CPU?
Thanks for your review, will fix it.
>
> You may occasionally put more than 63 characters into text lines
> of such a change description.
I checked the patch using ./scripts/checkpatch.pl before sending it, and
found no warnings or errors. The commit log should preferably have less
than 75 characters per line. If I'm wrong, please correct me, thank you.
Thanks,
Hao
next prev parent reply other threads:[~2024-12-24 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241223091446.90208-1-jiahao.kernel@gmail.com>
2024-12-23 20:50 ` [PATCH v2] sched/core: Prioritize migrating eligible tasks in sched_balance_rq() Markus Elfring
2024-12-24 1:53 ` Hao Jia [this message]
2024-12-24 8:55 ` [v2] " Markus Elfring
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=2cfea522-8015-d86b-f78d-a6a2c56ba8b8@gmail.com \
--to=jiahao.kernel@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jiahao1@lixiang.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--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