From: Mel Gorman <mgorman@techsingularity.net>
To: Hao Jia <jiahao.os@bytedance.com>
Cc: mingo@redhat.com, peterz@infradead.org, mingo@kernel.org,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
vschneid@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] sched/core: Adjusting the order of scanning CPU
Date: Mon, 14 Nov 2022 12:15:17 +0000 [thread overview]
Message-ID: <20221114121517.vwg4rr5xb3nvwpjy@techsingularity.net> (raw)
In-Reply-To: <20221026064300.78869-3-jiahao.os@bytedance.com>
On Wed, Oct 26, 2022 at 02:43:00PM +0800, Hao Jia wrote:
> When select_idle_capacity() starts scanning for an idle CPU, it starts
> with target CPU that has already been checked in select_idle_sibling().
> So we start checking from the next CPU and try the target CPU at the end.
> Similarly for task_numa_assign(), we have just checked numa_migrate_on
> of dst_cpu, so start from the next CPU. This also works for
> steal_cookie_task(), the first scan must fail and start directly
> from the next one.
>
> Signed-off-by: Hao Jia <jiahao.os@bytedance.com>
Test results in general look ok so
Acked-by: Mel Gorman <mgorman@techsingularity.net>
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2022-11-14 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 6:42 [PATCH v2 0/2] Clean up the process of scanning the CPU for some functions Hao Jia
2022-10-26 6:42 ` [PATCH v2 1/2] sched/numa: Stop an exhastive search if an idle core is found Hao Jia
2022-10-26 6:43 ` [PATCH v2 2/2] sched/core: Adjusting the order of scanning CPU Hao Jia
2022-11-14 12:15 ` Mel Gorman [this message]
2022-11-16 8:48 ` [External] " Hao Jia
2022-11-30 6:35 ` Hao Jia
2022-11-30 7:59 ` Vincent Guittot
2022-11-08 3:01 ` [PATCH v2 0/2] Clean up the process of scanning the CPU for some functions Hao Jia
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=20221114121517.vwg4rr5xb3nvwpjy@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jiahao.os@bytedance.com \
--cc=juri.lelli@redhat.com \
--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
all inboxes | Powered by JetHome®