From: Matt Fleming <matt@codeblueprint.co.uk>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, "Suthikulpanit,
Suravee" <Suravee.Suthikulpanit@amd.com>,
Mel Gorman <mgorman@techsingularity.net>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] sched/topology: Improve load balancing on AMD EPYC
Date: Mon, 10 Jun 2019 22:26:20 +0100 [thread overview]
Message-ID: <20190610212620.GA4772@codeblueprint.co.uk> (raw)
In-Reply-To: <20190605180035.GA3402@hirez.programming.kicks-ass.net>
On Wed, 05 Jun, at 08:00:35PM, Peter Zijlstra wrote:
>
> And then we had two magic values :/
>
> Should we not 'fix' RECLAIM_DISTANCE for EPYC or something? Because
> surely, if we want to load-balance agressively over 30, then so too
> should we do node_reclaim() I'm thikning.
Yeah we can fix it just for EPYC, Mel suggested that approach originally.
Suravee, Tom, what's the best way to detect these EPYC machines that need to
override RECLAIM_DISTANCE?
next prev parent reply other threads:[~2019-06-10 21:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 15:59 [PATCH] sched/topology: Improve load balancing on AMD EPYC Matt Fleming
2019-06-05 18:00 ` Peter Zijlstra
2019-06-10 21:26 ` Matt Fleming [this message]
2019-06-11 17:22 ` Lendacky, Thomas
2019-06-18 10:43 ` Matt Fleming
2019-06-18 12:33 ` Peter Zijlstra
2019-06-19 21:34 ` Matt Fleming
2019-06-24 14:24 ` Mel Gorman
2019-06-26 21:18 ` Suthikulpanit, Suravee
2019-06-28 15:15 ` Matt Fleming
2019-07-22 14:11 ` Suthikulpanit, Suravee
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=20190610212620.GA4772@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=peterz@infradead.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.