From: Tim Chen <tim.c.chen@linux.intel.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
Swapnil Sapkal <Swapnil.Sapkal@amd.com>,
Aaron Lu <aaron.lu@intel.com>,
Julien Desfossez <jdesfossez@digitalocean.com>,
x86@kernel.org
Subject: Re: [RFC PATCH 1/2] sched: Rate limit migrations to 1 per 2ms per task
Date: Tue, 05 Sep 2023 13:28:21 -0700 [thread overview]
Message-ID: <cfc3de8fa3172cedf406ccef8c94ef4da0a00281.camel@linux.intel.com> (raw)
In-Reply-To: <20230905171105.1005672-2-mathieu.desnoyers@efficios.com>
On Tue, 2023-09-05 at 13:11 -0400, Mathieu Desnoyers wrote:
> Rate limit migrations to 1 migration per 2 milliseconds per task. On a
> kernel with EEVDF scheduler (commit b97d64c722598ffed42ece814a2cb791336c6679),
> this speeds up hackbench from 62s to 45s on AMD EPYC 192-core (over 2 sockets).
>
>
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 479db611f46e..0d294fce261d 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -4510,6 +4510,7 @@ static void __sched_fork(unsigned long clone_flags, struct task_struct *p)
> p->se.vruntime = 0;
> p->se.vlag = 0;
> p->se.slice = sysctl_sched_base_slice;
> + p->se.next_migration_time = 0;
It seems like the next_migration_time should be initialized to the current time,
in case the system run for a long time and clock wrap around could cause problem.
> INIT_LIST_HEAD(&p->se.group_node);
>
> #ifdef CONFIG_FAIR_GROUP_SCHED
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index d92da2d78774..24ac69913005 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -960,6 +960,14 @@ int sched_update_scaling(void)
>
> static void clear_buddies(struct cfs_rq *cfs_rq, struct sched_entity *se);
>
> +static bool should_migrate_task(struct task_struct *p, int prev_cpu)
> +{
> + /* Rate limit task migration. */
> + if (sched_clock_cpu(prev_cpu) < p->se.next_migration_time)
Should we use time_before(sched_clock_cpu(prev_cpu), p->se.next_migration_time) ?
> + return false;
> + return true;
> +}
> +
Thanks.
Tim
next prev parent reply other threads:[~2023-09-05 20:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 17:11 [RFC PATCH 0/2] sched/eevdf: Rate limit task migration Mathieu Desnoyers
2023-09-05 17:11 ` [RFC PATCH 1/2] sched: Rate limit migrations to 1 per 2ms per task Mathieu Desnoyers
2023-09-05 20:28 ` Tim Chen [this message]
2023-09-05 21:16 ` Mathieu Desnoyers
2023-09-05 22:44 ` Tim Chen
2023-09-06 9:47 ` Peter Zijlstra
2023-09-06 20:51 ` Tim Chen
2023-09-06 21:55 ` Mathieu Desnoyers
2023-09-06 8:44 ` Peter Zijlstra
2023-09-06 13:58 ` Mathieu Desnoyers
2023-09-05 20:44 ` kernel test robot
2023-09-06 8:41 ` Peter Zijlstra
2023-09-06 13:57 ` Mathieu Desnoyers
2023-09-06 15:38 ` Mathieu Desnoyers
2023-09-10 7:03 ` Chen Yu
2023-09-13 15:46 ` Mathieu Desnoyers
2023-09-05 17:11 ` [RFC PATCH 2/2] sched: Implement adaptative rate limiting of task migrations Mathieu Desnoyers
2023-09-06 17:08 ` kernel test robot
2023-09-06 22:24 ` kernel test robot
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=cfc3de8fa3172cedf406ccef8c94ef4da0a00281.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=Swapnil.Sapkal@amd.com \
--cc=aaron.lu@intel.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=jdesfossez@digitalocean.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--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=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.