From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Yang Shi <shy828301@gmail.com>, Mel Gorman <mgorman@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Huang Ying <ying.huang@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Zi Yan <ziy@nvidia.com>,
zhongjiang-ali@linux.alibaba.com,
Xunlei Pang <xlpang@linux.alibaba.com>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] mm: Promote slow memory in advance to improve performance
Date: Tue, 23 Nov 2021 21:20:47 +0800 [thread overview]
Message-ID: <399f9ef5-3a77-902a-7b4c-86020e629944@linux.alibaba.com> (raw)
In-Reply-To: <CAHbLzkrj_GmmixNVhchbxqMWM3sCXdwr0eVhrs7BkLKZd1v8bg@mail.gmail.com>
On 2021/11/23 3:34, Yang Shi wrote:
> On Mon, Nov 22, 2021 at 2:22 AM Baolin Wang
> <baolin.wang@linux.alibaba.com> wrote:
>>
>> Some workloads access a set of data entities will follow the data locality,
>> also known as locality of reference, which means the probability of accessing
>> some data soon after some nearby data has been accessed.
>>
>> On some systems with different memory types, which will rely on the numa
>> balancing to promote slow hot memory to fast memory to improve performance.
>> So we can promote several sequential pages on slow memory at one time
>> according to the data locality for some workloads to improve the performance.
>
> Fault around for NUMA fault definitely could reduce the overhead for
> NUMA balancing by having fewer faults. I think this could be extended
> to regular NUMA balancing too. But I'm not sure whether false
> positives are worth concerning or not.
OK. Like Huang Ying said, maybe we can add some algorithm to adjust the
window of proactive numa faults dynamically. Thanks for your input.
>
> I recall Mel proposed fault around too (not in patch, but shared some
> ideas). Added Mel in this thread.
next prev parent reply other threads:[~2021-11-23 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 10:22 Baolin Wang
2021-11-22 19:34 ` Yang Shi
2021-11-23 13:20 ` Baolin Wang [this message]
2021-11-23 2:53 ` Huang, Ying
2021-11-23 13:27 ` Baolin Wang
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=399f9ef5-3a77-902a-7b4c-86020e629944@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=shy828301@gmail.com \
--cc=xlpang@linux.alibaba.com \
--cc=ying.huang@intel.com \
--cc=zhongjiang-ali@linux.alibaba.com \
--cc=ziy@nvidia.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