linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "benbjiang(蒋彪)" <benbjiang@tencent.com>
To: "Li, Aubrey" <aubrey.li@linux.intel.com>
Cc: Vineeth Remanan Pillai <vpillai@digitalocean.com>,
	Nishanth Aravamudan <naravamudan@digitalocean.com>,
	Julien Desfossez <jdesfossez@digitalocean.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"Tim Chen" <tim.c.chen@linux.intel.com>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"pjt@google.com" <pjt@google.com>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	Aubrey Li <aubrey.li@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"subhra.mazumdar@oracle.com" <subhra.mazumdar@oracle.com>,
	"fweisbec@gmail.com" <fweisbec@gmail.com>,
	"keescook@chromium.org" <keescook@chromium.org>,
	"kerrnel@google.com" <kerrnel@google.com>,
	Phil Auld <pauld@redhat.com>, Aaron Lu <aaron.lwe@gmail.com>,
	Aubrey Li <aubrey.intel@gmail.com>,
	Valentin Schneider <valentin.schneider@arm.com>,
	Mel Gorman <mgorman@techsingularity.net>,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Joel Fernandes <joelaf@google.com>,
	"joel@joelfernandes.org" <joel@joelfernandes.org>,
	"vineethrp@gmail.com" <vineethrp@gmail.com>,
	Chen Yu <yu.c.chen@intel.com>,
	Christian Brauner <christian.brauner@ubuntu.com>
Subject: Re: [RFC PATCH 11/16] sched: migration changes for core scheduling(Internet mail)
Date: Wed, 22 Jul 2020 14:32:36 +0000	[thread overview]
Message-ID: <5C71B460-8DC3-44AF-A75E-68BB2E33686B@tencent.com> (raw)
In-Reply-To: <459dbf33-02f6-d4e0-52e4-919e1e33be13@linux.intel.com>

Hi,

> On Jul 22, 2020, at 8:13 PM, Li, Aubrey <aubrey.li@linux.intel.com> wrote:
> 
> On 2020/7/22 16:54, benbjiang(蒋彪) wrote:
>> Hi, Aubrey,
>> 
>>> On Jul 1, 2020, at 5:32 AM, Vineeth Remanan Pillai <vpillai@digitalocean.com> wrote:
>>> 
>>> From: Aubrey Li <aubrey.li@intel.com>
>>> 
>>> - Don't migrate if there is a cookie mismatch
>>>    Load balance tries to move task from busiest CPU to the
>>>    destination CPU. When core scheduling is enabled, if the
>>>    task's cookie does not match with the destination CPU's
>>>    core cookie, this task will be skipped by this CPU. This
>>>    mitigates the forced idle time on the destination CPU.
>>> 
>>> - Select cookie matched idle CPU
>>>    In the fast path of task wakeup, select the first cookie matched
>>>    idle CPU instead of the first idle CPU.
>>> 
>>> - Find cookie matched idlest CPU
>>>    In the slow path of task wakeup, find the idlest CPU whose core
>>>    cookie matches with task's cookie
>>> 
>>> - Don't migrate task if cookie not match
>>>    For the NUMA load balance, don't migrate task to the CPU whose
>>>    core cookie does not match with task's cookie
>>> 
>>> Signed-off-by: Aubrey Li <aubrey.li@linux.intel.com>
>>> Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
>>> Signed-off-by: Vineeth Remanan Pillai <vpillai@digitalocean.com>
>>> ---
>>> kernel/sched/fair.c  | 64 ++++++++++++++++++++++++++++++++++++++++----
>>> kernel/sched/sched.h | 29 ++++++++++++++++++++
>>> 2 files changed, 88 insertions(+), 5 deletions(-)
>>> 
>>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>>> index d16939766361..33dc4bf01817 100644
>>> --- a/kernel/sched/fair.c
>>> +++ b/kernel/sched/fair.c
>>> @@ -2051,6 +2051,15 @@ static void task_numa_find_cpu(struct task_numa_env *env,
>>> 		if (!cpumask_test_cpu(cpu, env->p->cpus_ptr))
>>> 			continue;
>>> 
>>> +#ifdef CONFIG_SCHED_CORE
>>> +		/*
>>> +		 * Skip this cpu if source task's cookie does not match
>>> +		 * with CPU's core cookie.
>>> +		 */
>>> +		if (!sched_core_cookie_match(cpu_rq(cpu), env->p))
>>> +			continue;
>>> +#endif
>>> +
>>> 		env->dst_cpu = cpu;
>>> 		if (task_numa_compare(env, taskimp, groupimp, maymove))
>>> 			break;
>>> @@ -5963,11 +5972,17 @@ find_idlest_group_cpu(struct sched_group *group, struct task_struct *p, int this
>>> 
>>> 	/* Traverse only the allowed CPUs */
>>> 	for_each_cpu_and(i, sched_group_span(group), p->cpus_ptr) {
>>> +		struct rq *rq = cpu_rq(i);
>>> +
>>> +#ifdef CONFIG_SCHED_CORE
>>> +		if (!sched_core_cookie_match(rq, p))
>>> +			continue;
>>> +#endif
>>> +
>>> 		if (sched_idle_cpu(i))
>>> 			return i;
>>> 
>>> 		if (available_idle_cpu(i)) {
>>> -			struct rq *rq = cpu_rq(i);
>>> 			struct cpuidle_state *idle = idle_get_state(rq);
>>> 			if (idle && idle->exit_latency < min_exit_latency) {
>>> 				/*
>>> @@ -6224,8 +6239,18 @@ static int select_idle_cpu(struct task_struct *p, struct sched_domain *sd, int t
>>> 	for_each_cpu_wrap(cpu, cpus, target) {
>>> 		if (!--nr)
>>> 			return -1;
>>> -		if (available_idle_cpu(cpu) || sched_idle_cpu(cpu))
>>> -			break;
>>> +
>>> +		if (available_idle_cpu(cpu) || sched_idle_cpu(cpu)) {
>>> +#ifdef CONFIG_SCHED_CORE
>>> +			/*
>>> +			 * If Core Scheduling is enabled, select this cpu
>>> +			 * only if the process cookie matches core cookie.
>>> +			 */
>>> +			if (sched_core_enabled(cpu_rq(cpu)) &&
>>> +			    p->core_cookie == cpu_rq(cpu)->core->core_cookie)
>> Why not also add similar logic in select_idle_smt to reduce forced-idle? :)
> We hit select_idle_smt after we scaned the entire LLC domain for idle cores
> and idle cpus and failed,so IMHO, an idle smt is probably a good choice under
> this scenario.

AFAIC, selecting idle sibling with unmatched cookie will cause unnecessary fored-idle, unfairness and latency, compared to choosing *target* cpu.
Besides, choosing *target* cpu may be more cache friendly. So IMHO, *target* cpu may be a better choice if cookie not match, instead of idle sibling.

> 
>> 
>>> +#endif
>>> +				break;
>>> +		}
>>> 	}
>>> 
>>> 	time = cpu_clock(this) - time;
>>> @@ -7609,8 +7634,9 @@ int can_migrate_task(struct task_struct *p, struct lb_env *env)
>>> 	 * We do not migrate tasks that are:
>>> 	 * 1) throttled_lb_pair, or
>>> 	 * 2) cannot be migrated to this CPU due to cpus_ptr, or
>>> -	 * 3) running (obviously), or
>>> -	 * 4) are cache-hot on their current CPU.
>>> +	 * 3) task's cookie does not match with this CPU's core cookie
>>> +	 * 4) running (obviously), or
>>> +	 * 5) are cache-hot on their current CPU.
>>> 	 */
>>> 	if (throttled_lb_pair(task_group(p), env->src_cpu, env->dst_cpu))
>>> 		return 0;
>>> @@ -7645,6 +7671,15 @@ int can_migrate_task(struct task_struct *p, struct lb_env *env)
>>> 		return 0;
>>> 	}
>>> 
>>> +#ifdef CONFIG_SCHED_CORE
>>> +	/*
>>> +	 * Don't migrate task if the task's cookie does not match
>>> +	 * with the destination CPU's core cookie.
>>> +	 */
>>> +	if (!sched_core_cookie_match(cpu_rq(env->dst_cpu), p))
>>> +		return 0;
>>> +#endif
>>> +
>>> 	/* Record that we found atleast one task that could run on dst_cpu */
>>> 	env->flags &= ~LBF_ALL_PINNED;
>>> 
>>> @@ -8857,6 +8892,25 @@ find_idlest_group(struct sched_domain *sd, struct task_struct *p,
>>> 					p->cpus_ptr))
>>> 			continue;
>>> 
>>> +#ifdef CONFIG_SCHED_CORE
>>> +		if (sched_core_enabled(cpu_rq(this_cpu))) {
>>> +			int i = 0;
>>> +			bool cookie_match = false;
>>> +
>>> +			for_each_cpu(i, sched_group_span(group)) {
>> Should we consider the p->cpus_ptr here? like,
>> 			for_each_cpu_and(i, sched_group_span(group), p->cpus_ptr ) {
> 
> This is already considered just above #ifdef CONFIG_SCHED_CORE, but not included
> in the patch file.
> 
> Thanks,
> -Aubrey

The above consideration is,
 8893                 /* Skip over this group if it has no CPUs allowed */
 8894                 if (!cpumask_intersects(sched_group_span(group),
 8895                                         p->cpus_ptr))
 8896                         continue;
 8897
It only considers the case of *p is not allowed for the whole group*, which is not enough.
If( cpumask_subset(p->cpus_ptr, sched_group_span(group)), the following sched_core_cookie_match() may choose a *wrong(not allowed)* cpu to match cookie. In that case, the matching result could be confusing and lead to wrong result.
On the other hand, considering p->cpus_ptr here could reduce the loop times and cost, if cpumask_and(p->cpus_ptr, sched_group_span(group)) is the subset of sched_group_span(group).

Thx.
Regards,
Jiang

> 
>> 				...
>> 			}
>> Thx.
>> Regards,
>> Jiang
>> 
>>> +				struct rq *rq = cpu_rq(i);
>>> +
>>> +				if (sched_core_cookie_match(rq, p)) {
>>> +					cookie_match = true;
>>> +					break;
>>> +				}
>>> +			}
>>> +			/* Skip over this group if no cookie matched */
>>> +			if (!cookie_match)
>>> +				continue;
>>> +		}
>>> +#endif
>>> +
>>> 		local_group = cpumask_test_cpu(this_cpu,
>>> 					       sched_group_span(group));
>>> 
>>> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
>>> index 464559676fd2..875796d43fca 100644
>>> --- a/kernel/sched/sched.h
>>> +++ b/kernel/sched/sched.h
>>> @@ -1089,6 +1089,35 @@ static inline raw_spinlock_t *rq_lockp(struct rq *rq)
>>> bool cfs_prio_less(struct task_struct *a, struct task_struct *b);
>>> void sched_core_adjust_sibling_vruntime(int cpu, bool coresched_enabled);
>>> 
>>> +/*
>>> + * Helper to check if the CPU's core cookie matches with the task's cookie
>>> + * when core scheduling is enabled.
>>> + * A special case is that the task's cookie always matches with CPU's core
>>> + * cookie if the CPU is in an idle core.
>>> + */
>>> +static inline bool sched_core_cookie_match(struct rq *rq, struct task_struct *p)
>>> +{
>>> +	bool idle_core = true;
>>> +	int cpu;
>>> +
>>> +	/* Ignore cookie match if core scheduler is not enabled on the CPU. */
>>> +	if (!sched_core_enabled(rq))
>>> +		return true;
>>> +
>>> +	for_each_cpu(cpu, cpu_smt_mask(cpu_of(rq))) {
>>> +		if (!available_idle_cpu(cpu)) {
>>> +			idle_core = false;
>>> +			break;
>>> +		}
>>> +	}
>>> +
>>> +	/*
>>> +	 * A CPU in an idle core is always the best choice for tasks with
>>> +	 * cookies.
>>> +	 */
>>> +	return idle_core || rq->core->core_cookie == p->core_cookie;
>>> +}
>>> +
>>> extern void queue_core_balance(struct rq *rq);
>>> 
>>> #else /* !CONFIG_SCHED_CORE */
>>> -- 
>>> 2.17.1


  reply	other threads:[~2020-07-22 14:32 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 21:32 [RFC PATCH 00/16] Core scheduling v6 Vineeth Remanan Pillai
2020-06-30 21:32 ` [RFC PATCH 01/16] sched: Wrap rq::lock access Vineeth Remanan Pillai
2020-06-30 21:32 ` [RFC PATCH 02/16] sched: Introduce sched_class::pick_task() Vineeth Remanan Pillai
2020-06-30 21:32 ` [RFC PATCH 03/16] sched: Core-wide rq->lock Vineeth Remanan Pillai
2020-06-30 21:32 ` [RFC PATCH 04/16] sched/fair: Add a few assertions Vineeth Remanan Pillai
2020-06-30 21:32 ` [RFC PATCH 05/16] sched: Basic tracking of matching tasks Vineeth Remanan Pillai
2020-07-21 14:02   ` [RFC PATCH 05/16] sched: Basic tracking of matching tasks(Internet mail) benbjiang(蒋彪)
2020-06-30 21:32 ` [RFC PATCH 06/16] sched: Add core wide task selection and scheduling Vineeth Remanan Pillai
2020-07-01 23:28   ` Joel Fernandes
2020-07-02  0:54     ` Tim Chen
2020-07-02 12:57       ` Joel Fernandes
2020-07-02 13:23         ` Joel Fernandes
2020-07-05 23:44         ` Tim Chen
2020-07-03 20:21     ` Vineeth Remanan Pillai
2020-07-06 14:09       ` Joel Fernandes
2020-07-06 14:38         ` Vineeth Remanan Pillai
2020-07-06 17:37           ` Joel Fernandes
2020-06-30 21:32 ` [RFC PATCH 07/16] sched/fair: Fix forced idle sibling starvation corner case Vineeth Remanan Pillai
2020-07-21  7:35   ` [RFC PATCH 07/16] sched/fair: Fix forced idle sibling starvation corner case(Internet mail) benbjiang(蒋彪)
2020-07-22  7:20   ` benbjiang(蒋彪)
2020-06-30 21:32 ` [RFC PATCH 08/16] sched/fair: wrapper for cfs_rq->min_vruntime Vineeth Remanan Pillai
2020-06-30 21:32 ` [RFC PATCH 09/16] sched/fair: core wide cfs task priority comparison Vineeth Remanan Pillai
2020-07-22  0:23   ` [RFC PATCH 09/16] sched/fair: core wide cfs task priority comparison(Internet mail) benbjiang(蒋彪)
2020-07-24  7:14     ` Aaron Lu
2020-07-24 12:08       ` Jiang Biao
2020-06-30 21:32 ` [RFC PATCH 10/16] sched: Trivial forced-newidle balancer Vineeth Remanan Pillai
2020-07-20  4:06   ` [RFC PATCH 10/16] sched: Trivial forced-newidle balancer(Internet mail) benbjiang(蒋彪)
2020-07-20  6:06     ` Li, Aubrey
     [not found]       ` <8082F052-2F52-42D3-B396-18A35A94F26F@tencent.com>
2020-07-20  8:03         ` Li, Aubrey
2020-07-20  8:22           ` benbjiang(蒋彪)
2020-07-20 14:34   ` benbjiang(蒋彪)
2020-06-30 21:32 ` [RFC PATCH 11/16] sched: migration changes for core scheduling Vineeth Remanan Pillai
2020-07-22  8:54   ` [RFC PATCH 11/16] sched: migration changes for core scheduling(Internet mail) benbjiang(蒋彪)
2020-07-22 12:13     ` Li, Aubrey
2020-07-22 14:32       ` benbjiang(蒋彪) [this message]
2020-07-23  1:57         ` Li, Aubrey
2020-07-23  2:42           ` benbjiang(蒋彪)
2020-07-23  3:35             ` Li, Aubrey
2020-07-23  4:23               ` benbjiang(蒋彪)
2020-07-23  5:39                 ` Li, Aubrey
2020-07-23  7:47                   ` benbjiang(蒋彪)
2020-07-23  8:06                     ` Li, Aubrey
2020-07-23  8:28                       ` benbjiang(蒋彪)
2020-07-23 23:43                         ` Aubrey Li
2020-07-24  1:26                           ` benbjiang(蒋彪)
2020-07-24  2:05                             ` Li, Aubrey
2020-07-24  2:29                               ` benbjiang(蒋彪)
2020-06-30 21:32 ` [RFC PATCH 12/16] sched: cgroup tagging interface for core scheduling Vineeth Remanan Pillai
2020-06-30 21:32 ` [RFC PATCH 13/16] sched: Fix pick_next_task() race condition in " Vineeth Remanan Pillai
2020-06-30 21:32 ` [RFC PATCH 14/16] irq: Add support for core-wide protection of IRQ and softirq Vineeth Remanan Pillai
2020-07-10 12:19   ` Li, Aubrey
2020-07-10 13:21     ` Joel Fernandes
2020-07-13  2:23       ` Li, Aubrey
2020-07-13 15:58         ` Joel Fernandes
2020-07-10 13:36     ` Vineeth Remanan Pillai
2020-07-11  1:33       ` Aubrey Li
2020-07-17 23:37     ` Thomas Gleixner
2020-07-18 17:05       ` Joel Fernandes
2020-07-17 23:36   ` Thomas Gleixner
2020-07-20  3:53     ` Joel Fernandes
2020-07-20  8:20       ` Thomas Gleixner
2020-07-20 11:09       ` Vineeth Pillai
2020-06-30 21:32 ` [RFC PATCH 15/16] Documentation: Add documentation on core scheduling Vineeth Remanan Pillai
2020-06-30 21:32 ` [RFC PATCH 16/16] sched: Debug bits Vineeth Remanan Pillai
2020-07-31 16:41 ` [RFC PATCH 00/16] Core scheduling v6 Vineeth Pillai
2020-08-03  8:23 ` Li, Aubrey
2020-08-03 16:53   ` Joel Fernandes
2020-08-05  3:57     ` Li, Aubrey
2020-08-05  6:16       ` [RFC PATCH 00/16] Core scheduling v6(Internet mail) benbjiang(蒋彪)
2020-08-09 16:44       ` [RFC PATCH 00/16] Core scheduling v6 Joel Fernandes
2020-08-12  2:01         ` Li, Aubrey
2020-08-12 23:08           ` Joel Fernandes
2020-08-13  4:28             ` Li, Aubrey
2020-08-14  0:26               ` [RFC PATCH 00/16] Core scheduling v6(Internet mail) benbjiang(蒋彪)
2020-08-14  1:36                 ` Li, Aubrey
2020-08-14  4:04                   ` benbjiang(蒋彪)
2020-08-14  5:18                     ` Li, Aubrey
2020-08-14  7:54                       ` benbjiang(蒋彪)
2020-08-20 22:37               ` [RFC PATCH 00/16] Core scheduling v6 Joel Fernandes
2020-08-27  0:30 ` Alexander Graf
2020-08-27  1:20   ` Vineeth Pillai

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=5C71B460-8DC3-44AF-A75E-68BB2E33686B@tencent.com \
    --to=benbjiang@tencent.com \
    --cc=aaron.lwe@gmail.com \
    --cc=aubrey.intel@gmail.com \
    --cc=aubrey.li@intel.com \
    --cc=aubrey.li@linux.intel.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=fweisbec@gmail.com \
    --cc=jdesfossez@digitalocean.com \
    --cc=joel@joelfernandes.org \
    --cc=joelaf@google.com \
    --cc=keescook@chromium.org \
    --cc=kerrnel@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mingo@kernel.org \
    --cc=naravamudan@digitalocean.com \
    --cc=pauld@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=subhra.mazumdar@oracle.com \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=valentin.schneider@arm.com \
    --cc=vineethrp@gmail.com \
    --cc=vpillai@digitalocean.com \
    --cc=yu.c.chen@intel.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;
as well as URLs for NNTP newsgroup(s).