From: "Huang, Ying" <ying.huang@intel.com>
To: Dave Hansen <dave.hansen@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, 05 Nov 2021 10:51:31 +0800 [thread overview]
Message-ID: <87tugrxqks.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <665cb882-6dbc-335f-1435-e52659d7ee58@intel.com> (Dave Hansen's message of "Thu, 4 Nov 2021 08:18:02 -0700")
Dave Hansen <dave.hansen@intel.com> writes:
> On 11/4/21 2:13 AM, Baolin Wang wrote:
>> +What: /sys/kernel/mm/numa/demotion_mode
>> +Date: November 2021
>> +Contact: Linux memory management mailing list <linux-mm@kvack.org>
>> +Description: Set the demotion mode when enabling demoting pages during reclaim
>
> I don't think we need a tunable for this. The existing behavior is just
> stupid for your hardware and can be replaced.
Yes. I think so too. I don't think DIRECT_DEMOTION is reasonable for your system.
> 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.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2021-11-05 2:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 9:13 Baolin Wang
2021-11-04 15:18 ` Dave Hansen
2021-11-05 2:51 ` Huang, Ying [this message]
2021-11-05 15:47 ` Dave Hansen
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=87tugrxqks.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dave.hansen@intel.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=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