From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Chuyi Zhou <zhouchuyi@bytedance.com>, <mingo@redhat.com>,
<peterz@infradead.org>, <juri.lelli@redhat.com>,
<vincent.guittot@linaro.org>, <dietmar.eggemann@arm.com>,
<rostedt@goodmis.org>, <bsegall@google.com>, <mgorman@suse.de>,
<vschneid@redhat.com>
Cc: <chengming.zhou@linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] sched/fair: Remove unused task_numa_migrate return value
Date: Wed, 18 Dec 2024 11:59:19 +0530 [thread overview]
Message-ID: <2bda56c3-727f-4899-8d88-fd83f11b3e76@amd.com> (raw)
In-Reply-To: <20241216122357.1276382-2-zhouchuyi@bytedance.com>
Hello Chuyi,
On 12/16/2024 5:53 PM, Chuyi Zhou wrote:
> The return value of task_numa_migrate is unused, remove it.
>
> Signed-off-by: Chuyi Zhou <zhouchuyi@bytedance.com>
Feel free to include:
Reviewed-by: K Prateek Nayak <kprateek.nayak@amd.com>
If anyone cares for the history, initial NUMA Balancing implementation
used the return value of task_numa_migrate() to retry NUMA Balancing in
commit 6b9a7460b6ba ("sched/numa: Retry migration of tasks to CPU on a
preferred node") however in the same series[1], Mel also included an
optimization from Rik which retried NUMA Balancing periodically
irrespective the return value from task_numa_migrate() in commit
2739d3eef3a9 ("sched/numa: Retry task_numa_migrate() periodically")
[1] https://lore.kernel.org/all/1381141781-10992-34-git-send-email-mgorman@suse.de/
--
Thanks and Regards,
Prateek
> ---
> kernel/sched/fair.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index d5127d9beaea..f544012b9320 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -2486,7 +2486,7 @@ static void task_numa_find_cpu(struct task_numa_env *env,
> }
> }
>
> -static int task_numa_migrate(struct task_struct *p)
> +static void task_numa_migrate(struct task_struct *p)
> {
> struct task_numa_env env = {
> .p = p,
> @@ -2531,7 +2531,7 @@ static int task_numa_migrate(struct task_struct *p)
> */
> if (unlikely(!sd)) {
> sched_setnuma(p, task_node(p));
> - return -EINVAL;
> + return;
> }
>
> env.dst_nid = p->numa_preferred_nid;
> @@ -2600,7 +2600,7 @@ static int task_numa_migrate(struct task_struct *p)
> /* No better CPU than the current one was found. */
> if (env.best_cpu == -1) {
> trace_sched_stick_numa(p, env.src_cpu, NULL, -1);
> - return -EAGAIN;
> + return;
> }
>
> best_rq = cpu_rq(env.best_cpu);
> @@ -2609,7 +2609,7 @@ static int task_numa_migrate(struct task_struct *p)
> WRITE_ONCE(best_rq->numa_migrate_on, 0);
> if (ret != 0)
> trace_sched_stick_numa(p, env.src_cpu, NULL, env.best_cpu);
> - return ret;
> + return;
> }
>
> ret = migrate_swap(p, env.best_task, env.best_cpu, env.src_cpu);
> @@ -2618,7 +2618,6 @@ static int task_numa_migrate(struct task_struct *p)
> if (ret != 0)
> trace_sched_stick_numa(p, env.src_cpu, env.best_task, env.best_cpu);
> put_task_struct(env.best_task);
> - return ret;
> }
>
> /* Attempt to migrate a task to a CPU on the preferred node. */
next prev parent reply other threads:[~2024-12-18 6:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 12:23 [PATCH 0/3] Take the scheduling domain into account in numa balancing Chuyi Zhou
2024-12-16 12:23 ` [PATCH 1/3] sched/fair: Remove unused task_numa_migrate return value Chuyi Zhou
2024-12-18 6:29 ` K Prateek Nayak [this message]
2024-12-23 12:34 ` Chuyi Zhou
2024-12-16 12:23 ` [PATCH 2/3] sched/fair: Ignore isolated cpus in update_numa_stat Chuyi Zhou
2024-12-18 6:26 ` K Prateek Nayak
2024-12-18 7:19 ` [External] " Chuyi Zhou
2024-12-16 12:23 ` [PATCH 3/3] sched/fair: Ensure select housekeeping cpus in task_numa_find_cpu Chuyi Zhou
2024-12-18 6:21 ` K Prateek Nayak
2024-12-23 12:58 ` Chuyi Zhou
2024-12-27 4:40 ` K Prateek Nayak
2024-12-27 7:59 ` Chuyi Zhou
2025-01-02 5:49 ` K Prateek Nayak
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=2bda56c3-727f-4899-8d88-fd83f11b3e76@amd.com \
--to=kprateek.nayak@amd.com \
--cc=bsegall@google.com \
--cc=chengming.zhou@linux.dev \
--cc=dietmar.eggemann@arm.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 \
--cc=zhouchuyi@bytedance.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®