[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20230512094946.2639893-1-zhaomzhao@126.com>
Date: Fri, 12 May 2023 05:49:46 -0400
From: zhaomzhao@....com
To: mingo@...hat.com, peterz@...radead.org, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
bristot@...hat.com, vschneid@...hat.com
Cc: linux-kernel@...r.kernel.org,
Zhao Mengmeng <zhaomengmeng@...inos.cn>
Subject: [PATCH v1] sched/numa: init numa_scan_period with sysctl_numa_balancing_scan_period_min
From: Zhao Mengmeng <zhaomengmeng@...inos.cn>
As the name suggests, sysctl_numa_balancing_scan_delay is a "delay"
mainly used by numa_next_scan, it has nothing to do with scan period. So
init numa_scan_period with sysctl_numa_balancing_scan_period_min.
Signed-off-by: Zhao Mengmeng <zhaomengmeng@...inos.cn>
---
kernel/sched/fair.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 373ff5f55884..9b7d4f3a3d50 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -3149,7 +3149,7 @@ void init_numa_balancing(unsigned long clone_flags, struct task_struct *p)
}
p->node_stamp = 0;
p->numa_scan_seq = mm ? mm->numa_scan_seq : 0;
- p->numa_scan_period = sysctl_numa_balancing_scan_delay;
+ p->numa_scan_period = sysctl_numa_balancing_scan_period_min;
p->numa_migrate_retry = 0;
/* Protect against double add, see task_tick_numa and task_numa_work */
p->numa_work.next = &p->numa_work;
--
2.38.1
Powered by blists - more mailing lists