From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
jhladky@redhat.com, lvenanci@redhat.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RESEND] autonuma: Fix scan period updating
Date: Fri, 26 Jul 2019 14:50:21 +0530 [thread overview]
Message-ID: <20190726092021.GA5273@linux.vnet.ibm.com> (raw)
In-Reply-To: <87y30l5jdo.fsf@yhuang-dev.intel.com>
* Huang, Ying <ying.huang@intel.com> [2019-07-26 15:45:39]:
> Hi, Srikar,
>
> >
> > More Remote + Private page Accesses:
> > Most likely the Private accesses are going to be local accesses.
> >
> > In the unlikely event of the private accesses not being local, we should
> > scan faster so that the memory and task consolidates.
> >
> > More Remote + Shared page Accesses: This means the workload has not
> > consolidated and needs to scan faster. So we need to scan faster.
>
> This sounds reasonable. But
>
> lr_ratio < NUMA_PERIOD_THRESHOLD
>
> doesn't indicate More Remote. If Local = Remote, it is also true. If
less lr_ratio means more remote.
> there are also more Shared, we should slow down the scanning. So, the
Why should we slowing down if there are more remote shared accesses?
> logic could be
>
> if (lr_ratio >= NUMA_PERIOD_THRESHOLD)
> slow down scanning
> else if (sp_ratio >= NUMA_PERIOD_THRESHOLD) {
> if (NUMA_PERIOD_SLOTS - lr_ratio >= NUMA_PERIOD_THRESHOLD)
> speed up scanning
> else
> slow down scanning
> } else
> speed up scanning
>
> This follows your idea better?
>
> Best Regards,
> Huang, Ying
--
Thanks and Regards
Srikar Dronamraju
next prev parent reply other threads:[~2019-07-26 9:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 8:01 Huang, Ying
2019-07-25 17:35 ` Srikar Dronamraju
2019-07-26 7:45 ` Huang, Ying
2019-07-26 9:20 ` Srikar Dronamraju [this message]
2019-07-29 3:04 ` Huang, Ying
2019-07-29 7:28 ` Srikar Dronamraju
2019-07-29 8:16 ` Huang, Ying
2019-07-29 8:56 ` Mel Gorman
2019-07-30 1:38 ` Huang, Ying
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=20190726092021.GA5273@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=jhladky@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lvenanci@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=ying.huang@intel.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