From: Jagdish Gediya <jvgediya@linux.ibm.com>
To: "ying.huang@intel.com" <ying.huang@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, baolin.wang@linux.alibaba.com,
dave.hansen@linux.intel.com, aneesh.kumar@linux.ibm.com,
shy828301@gmail.com, weixugc@google.com, gthelen@google.com,
dan.j.williams@intel.com
Subject: Re: [PATCH v3 1/7] mm: demotion: Fix demotion targets sharing among sources
Date: Mon, 25 Apr 2022 15:02:08 +0530 [thread overview]
Message-ID: <YmZqmEyEcs3wwu2a@li-6e1fa1cc-351b-11b2-a85c-b897023bb5f3.ibm.com> (raw)
In-Reply-To: <bb4daddde2df1762dd0d6f2faac1d196a01d50be.camel@intel.com>
On Sun, Apr 24, 2022 at 11:25:50AM +0800, ying.huang@intel.com wrote:
> > Subject: [PATCH v3 1/7] mm: demotion: Fix demotion targets sharing among sources
>
> IMHO, this patch doesn't fix some bugs in the original code. Instead,
> it just enhances the original code. For example, the subject could be,
I think it is fixing a bug, there is a comment in the code which
mentions that 'used_targets will become unavailable in future passes.
This limits some opportunities for multiple source nodes to share a
destination'. As per this comment, it was intended to share a node as
demotion targets with some limits but the code limits not some but all
such opportunities as no common node can be demotion targets for
multiple source node as per current code.
> mm: demotion: support to share demotion targets among sources
>
> Best Regards,
> Huang, Ying
>
> [snip]
>
>
>
next prev parent reply other threads:[~2022-04-25 9:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 19:55 [PATCH v3 0/7] mm: demotion: Introduce new node state N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 19:55 ` [PATCH v3 1/7] mm: demotion: Fix demotion targets sharing among sources Jagdish Gediya
2022-04-24 3:25 ` ying.huang
2022-04-25 9:32 ` Jagdish Gediya [this message]
2022-04-26 7:26 ` ying.huang
2022-04-22 19:55 ` [PATCH v3 2/7] mm: demotion: Add new node state N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 20:29 ` Wei Xu
2022-04-22 19:55 ` [PATCH v3 3/7] drivers/base/node: Add support to write node_states[] via sysfs Jagdish Gediya
2022-04-22 20:32 ` Wei Xu
2022-04-24 6:25 ` Aneesh Kumar K.V
2022-04-25 9:42 ` Jagdish Gediya
2022-04-24 6:29 ` ying.huang
2022-04-22 19:55 ` [PATCH v3 4/7] device-dax/kmem: Set node state as N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 20:34 ` Wei Xu
2022-04-22 19:55 ` [PATCH v3 5/7] mm: demotion: Build demotion list based on N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 20:39 ` Wei Xu
2022-04-22 19:55 ` [PATCH v3 6/7] mm: demotion: expose per-node demotion targets via sysfs Jagdish Gediya
2022-04-22 20:47 ` Wei Xu
2022-04-23 7:30 ` kernel test robot
2022-04-23 8:38 ` kernel test robot
2022-04-22 19:55 ` [PATCH v3 7/7] docs: numa: Add documentation for demotion Jagdish Gediya
2022-04-24 3:19 ` [PATCH v3 0/7] mm: demotion: Introduce new node state N_DEMOTION_TARGETS ying.huang
2022-04-25 11:15 ` Jagdish Gediya
2022-04-25 13:57 ` Jonathan Cameron
2022-04-25 14:44 ` Aneesh Kumar K V
2022-04-26 10:43 ` Jonathan Cameron
2022-04-27 1:29 ` ying.huang
2022-04-27 2:57 ` Aneesh Kumar K V
2022-04-27 3:34 ` ying.huang
2022-04-25 14:53 ` Aneesh Kumar K V
2022-04-26 10:37 ` Jonathan Cameron
2022-04-26 7:55 ` ying.huang
2022-04-26 9:07 ` Aneesh Kumar K V
2022-04-26 9:10 ` ying.huang
2022-04-26 9:37 ` Jagdish Gediya
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=YmZqmEyEcs3wwu2a@li-6e1fa1cc-351b-11b2-a85c-b897023bb5f3.ibm.com \
--to=jvgediya@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gthelen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=weixugc@google.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;
as well as URLs for NNTP newsgroup(s).