linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: Yang Shi <shy828301@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>, Rik van Riel <riel@surriel.com>,
	Mel Gorman <mgorman@suse.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Zi Yan <ziy@nvidia.com>, Wei Xu <weixugc@google.com>,
	osalvador <osalvador@suse.de>, Shakeel Butt <shakeelb@google.com>,
	Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH -V8 2/6] memory tiering: add page promotion counter
Date: Wed, 15 Sep 2021 09:53:16 +0800	[thread overview]
Message-ID: <87y27y1u5v.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <CAHbLzkqhA0YJncxYokViaAa1Eo5RuMjiRmqGYb_=QAniYBd-bA@mail.gmail.com> (Yang Shi's message of "Tue, 14 Sep 2021 15:41:49 -0700")

Yang Shi <shy828301@gmail.com> writes:

> On Mon, Sep 13, 2021 at 6:37 PM Huang Ying <ying.huang@intel.com> wrote:
>>
>> To distinguish the number of the memory tiering promoted pages from
>> that of the originally inter-socket NUMA balancing migrated pages.
>> The counter is per-node (count in the target node).  So this can be
>> used to identify promotion imbalance among the NUMA nodes.
>
> I'd like this patch be the very first one in the series. Since we need
> such counters regardless of all the optimizations. And actually I
> think this patch could go with the merged "migration in lieu of
> discard" patchset.

Yes.  This sounds reasonable.  I will change this in the next version.

Best Regards,
Huang, Ying

  reply	other threads:[~2021-09-15  1:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14  1:36 [PATCH -V8 0/6] NUMA balancing: optimize memory placement for memory tiering system Huang Ying
2021-09-14  1:36 ` [PATCH -V8 1/6] NUMA balancing: optimize page " Huang Ying
2021-09-14 22:40   ` Yang Shi
2021-09-15  1:44     ` Huang, Ying
2021-09-15  2:47       ` Yang Shi
2021-09-15  3:58         ` Huang, Ying
2021-09-15 21:32           ` Yang Shi
2021-09-16  1:44             ` Huang, Ying
2021-09-17  0:47               ` Yang Shi
2021-09-17  1:24                 ` Huang, Ying
2021-09-14  1:36 ` [PATCH -V8 2/6] memory tiering: add page promotion counter Huang Ying
2021-09-14 22:41   ` Yang Shi
2021-09-15  1:53     ` Huang, Ying [this message]
2021-09-14  1:36 ` [PATCH -V8 3/6] memory tiering: skip to scan fast memory Huang Ying
2021-09-14  1:36 ` [PATCH -V8 4/6] memory tiering: hot page selection with hint page fault latency Huang Ying
2021-09-14  1:37 ` [PATCH -V8 5/6] memory tiering: rate limit NUMA migration throughput Huang Ying
2021-09-14  1:37 ` [PATCH -V8 6/6] memory tiering: adjust hot threshold automatically 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=87y27y1u5v.fsf@yhuang6-desk2.ccr.corp.intel.com \
    --to=ying.huang@intel.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=mhocko@suse.com \
    --cc=osalvador@suse.de \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=shakeelb@google.com \
    --cc=shy828301@gmail.com \
    --cc=weixugc@google.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;
as well as URLs for NNTP newsgroup(s).