linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>
Cc: linux-kernel@vger.kernel.org, mgorman@techsingularity.net,
	peterz@infradead.org, linux-mm@kvack.org,
	vincent.guittot@linaro.org
Subject: Re: [PATCH 5/5] sched/fair: Add exception for hints in load balancing path
Date: Sun, 11 Sep 2022 16:05:47 +0800	[thread overview]
Message-ID: <20220911080547.2709-1-hdanton@sina.com> (raw)
In-Reply-To: <20220910105326.1797-6-kprateek.nayak@amd.com>

On 10 Sep 2022 16:23:26 +0530 K Prateek Nayak <kprateek.nayak@amd.com> wrote:
> - Load balancing considerations
> 
> If we have more tasks than the CPUs in the MC Domain, ignore the hint
> set by the user. This prevents losing the consolidation done at the
> wakeup time.

It is waste of time to cure ten pains with a pill in five days a week.

> @@ -7977,6 +7980,21 @@ int can_migrate_task(struct task_struct *p, struct lb_env *env)
>  		return 0;
>  	}
>  
> +	/*
> +	 * Hints are followed only if the MC Domain is still ideal
> +	 * for the task.
> +	 */
> +	if (!env->ignore_hint) {
> +		/*
> +		 * Only consider the hints from the wakeup path to maintain
> +		 * data locality.
> +		 */
> +		if (READ_ONCE(p->hint) &
> +		    (PR_SCHED_HINT_WAKE_AFFINE | PR_SCHED_HINT_WAKE_HOLD))
> +			return 0;
> +	}

The wake hints are not honored during lb without PR_SCHED_HINT_IGNORE_LB set
then the scheduler works as you hint.

Hillf


       reply	other threads:[~2022-09-11  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220910105326.1797-1-kprateek.nayak@amd.com>
     [not found] ` <20220910105326.1797-6-kprateek.nayak@amd.com>
2022-09-11  8:05   ` Hillf Danton [this message]
2022-09-12  6:29     ` K Prateek Nayak
2022-09-12  8:55       ` Hillf Danton

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=20220911080547.2709-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=peterz@infradead.org \
    --cc=vincent.guittot@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox