From: Dave Hansen <dave.hansen@intel.com>
To: "Huang, Ying" <ying.huang@intel.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: akpm@linux-foundation.org, dave.hansen@linux.intel.com,
ziy@nvidia.com, osalvador@suse.de, shy828301@gmail.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] mm: migrate: Add new node demotion strategy
Date: Fri, 5 Nov 2021 08:47:23 -0700 [thread overview]
Message-ID: <c0023ae8-0aff-0890-00fb-310d72130f8a@intel.com> (raw)
In-Reply-To: <87tugrxqks.fsf@yhuang6-desk2.ccr.corp.intel.com>
On 11/4/21 7:51 PM, Huang, Ying wrote:
>> Let's also try to do it with the existing node_demotion[] data
>> structure before we go adding more.
> To avoid cache ping-pong, I guess some kind of per-CPU data structure
> may be more suitable for interleaving among multiple nodes.
It would probably be better to just find something that's more
read-heavy. Like, instead of keeping a strict round-robin, just
randomly select one of the notes to which you can round-robin.
That will scale naturally without having to worry about caching or fancy
per-cpu data structures.
next prev parent reply other threads:[~2021-11-05 15:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 9:13 [RFC PATCH] mm: migrate: Add new node demotion strategy Baolin Wang
2021-11-04 15:18 ` Dave Hansen
2021-11-05 2:51 ` Huang, Ying
2021-11-05 15:47 ` Dave Hansen [this message]
2021-11-07 9:33 ` Baolin Wang
2021-11-07 15:20 ` Dave Hansen
2021-11-08 6:38 ` Baolin Wang
2021-11-08 6:48 ` Huang, Ying
2021-11-08 7:07 ` Baolin Wang
2021-11-08 8:12 ` Huang, Ying
2021-11-08 8:43 ` Baolin Wang
2021-11-08 2:12 ` 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=c0023ae8-0aff-0890-00fb-310d72130f8a@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=ying.huang@intel.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 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.