From: Dave Hansen <dave.hansen@intel.com>
To: Jagdish Gediya <jvgediya@linux.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, aneesh.kumar@linux.ibm.com,
baolin.wang@linux.alibaba.com, dave.hansen@linux.intel.com,
ying.huang@intel.com
Subject: Re: [PATCH] mm: migrate: set demotion targets differently
Date: Tue, 29 Mar 2022 07:31:12 -0700 [thread overview]
Message-ID: <55161160-1084-c81d-d116-00f5bcaa1268@intel.com> (raw)
In-Reply-To: <20220329115222.8923-1-jvgediya@linux.ibm.com>
On 3/29/22 04:52, Jagdish Gediya wrote:
> The current implementation to identify the demotion
> targets limits some of the opportunities to share
> the demotion targets between multiple source nodes.
This changelog is a bit unsatisfying. It basically says: the current
code isn't working, throw some more code at the problem.
I'd love to see some more information about *why* the current code
doesn't work. Is it purely a bug or was it mis-designed?
I actually wrote it intending for it to handle cases like you describe
while not leaving lots of nodes without demotion targets.
next prev parent reply other threads:[~2022-03-29 14:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 11:52 [PATCH] mm: migrate: set demotion targets differently Jagdish Gediya
2022-03-29 12:26 ` Baolin Wang
2022-03-29 14:04 ` Jagdish Gediya
2022-03-30 6:37 ` Baolin Wang
2022-03-30 6:54 ` Huang, Ying
2022-03-29 14:31 ` Dave Hansen [this message]
2022-03-29 16:46 ` Jagdish Gediya
2022-03-29 22:40 ` Dave Hansen
2022-03-30 6:46 ` Huang, Ying
2022-03-30 16:36 ` Jagdish Gediya
2022-03-31 0:27 ` Huang, Ying
2022-03-31 11:17 ` Jonathan Cameron
2022-03-30 17:17 ` Aneesh Kumar K.V
2022-03-31 0:32 ` Huang, Ying
2022-03-31 6:45 ` Aneesh Kumar K.V
2022-03-31 7:23 ` Huang, Ying
2022-03-31 8:27 ` Aneesh Kumar K.V
2022-03-31 8:58 ` Huang, Ying
2022-03-31 9:33 ` 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=55161160-1084-c81d-d116-00f5bcaa1268@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=dave.hansen@linux.intel.com \
--cc=jvgediya@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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;
as well as URLs for NNTP newsgroup(s).