From: "Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Mel Gorman <mgorman@techsingularity.net>,
Peter Zijlstra <peterz@infradead.org>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] sched/topology: Improve load balancing on AMD EPYC
Date: Mon, 22 Jul 2019 14:11:12 +0000 [thread overview]
Message-ID: <35845e45-0513-085f-9848-3dca92391c76@amd.com> (raw)
In-Reply-To: <20190628151508.GB6909@codeblueprint.co.uk>
Matt
On 6/28/2019 10:15 AM, Matt Fleming wrote:
> On Wed, 26 Jun, at 09:18:01PM, Suthikulpanit, Suravee wrote:
>>
>> We use 16 to designate 1-hop latency (for different node within the same socket).
>> For across-socket access, since the latency is greater, we set the latency to 32
>> (twice the latency of 1-hop) not aware of the RECLAIM_DISTANCE at the time.
>
> I guess the question is: Is the memory latency of a remote node 1 hop
> away 1.6x the local node latency?
>
Yes, remote node 1 hop is 1.6x the local node latency for AMD EPYC.
Suravee
prev parent reply other threads:[~2019-07-22 14:11 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
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 [this message]
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=35845e45-0513-085f-9848-3dca92391c76@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--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 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).