From: Peter Zijlstra <peterz@infradead.org>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org, mgorman@suse.de, mingo@kernel.org
Subject: Re: [PATCH] sched,numa: always try to migrate to preferred node at task_numa_placement time
Date: Tue, 10 Jun 2014 17:07:55 +0200 [thread overview]
Message-ID: <20140610150755.GK6758@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <5392072D.6040605@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
On Fri, Jun 06, 2014 at 02:23:41PM -0400, Rik van Riel wrote:
> On 06/06/2014 01:18 PM, Peter Zijlstra wrote:
> > Clearly the retry thing didn't work, what happened? We got to the
> > preferred nid, disabled the retry and got moved away again?
> >
> > Do we want to remove the retry logic in favour of this more aggressive
> > form?
>
> I think we want both. When we have fresh statistics, and we discover
> that we are not running on our preferred nid, is there any reason
> not to relocate to a better node?
I got confused on the exact details, I thought we ended up calling
task_numa_placement() far often than we actually do (well, we do call it
as often, but bail early).
Yes this makes sense.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-06-10 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 20:33 [PATCH] sched,numa: always try to migrate to preferred node at task_numa_placement time Rik van Riel
2014-06-06 17:18 ` Peter Zijlstra
2014-06-06 18:23 ` Rik van Riel
2014-06-10 15:07 ` Peter Zijlstra [this message]
2014-06-19 12:36 ` [tip:sched/core] sched/numa: Always try to migrate to preferred node at task_numa_placement() time tip-bot for Rik van Riel
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=20140610150755.GK6758@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=riel@redhat.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