From: Johannes Weiner <hannes@cmpxchg.org>
To: Ying Huang <ying.huang@intel.com>
Cc: linux-mm@kvack.org, Hao Wang <haowang3@fb.com>,
Abhishek Dhanotia <abhishekd@fb.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Yang Shi <yang.shi@linux.alibaba.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Adam Manzanares <a.manzanares@samsung.com>,
linux-kernel@vger.kernel.org, kernel-team@fb.com,
Hasan Al Maruf <hasanalmaruf@fb.com>, Wei Xu <weixugc@google.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Yang Shi <shy828301@gmail.com>
Subject: Re: [PATCH] mm: mempolicy: N:M interleave policy for tiered memory nodes
Date: Wed, 8 Jun 2022 10:16:12 -0400 [thread overview]
Message-ID: <YqCvLM/ZMupRPpXP@cmpxchg.org> (raw)
In-Reply-To: <dece66a05bb63a04706d25ca86f75bfc875c27fd.camel@intel.com>
On Wed, Jun 08, 2022 at 12:19:52PM +0800, Ying Huang wrote:
> In general, I think the use case is valid.
Excellent!
> But we are changing memory tiering now, including
>
> - make memory tiering explict
>
> - support more than 2 tiers
>
> - expose memory tiering via sysfs
>
> Details can be found int the following threads,
>
> https://lore.kernel.org/lkml/CAAPL-u9Wv+nH1VOZTj=9p9S70Y3Qz3+63EkqncRDdHfubsrjfw@mail.gmail.com/
> https://lore.kernel.org/lkml/20220603134237.131362-1-aneesh.kumar@linux.ibm.com/
>
> With these changes, we may need to revise your implementation. For
> example, put interleave knobs in memory tier sysfs interface, support
> more than 2 tiers, etc.
Yeah, I was expecting the interface to be the main sticking point ;)
I'll rebase this patch as the mentioned discussions find consensus.
Thanks!
next prev parent reply other threads:[~2022-06-08 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 17:19 [PATCH] mm: mempolicy: N:M interleave policy for tiered memory nodes Johannes Weiner
2022-06-08 4:19 ` Ying Huang
2022-06-08 14:16 ` Johannes Weiner [this message]
2022-06-08 18:15 ` Tim Chen
2022-06-08 19:14 ` Johannes Weiner
2022-06-08 23:40 ` Tim Chen
2022-06-08 23:44 ` kernel test robot
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=YqCvLM/ZMupRPpXP@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=a.manzanares@samsung.com \
--cc=abhishekd@fb.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=haowang3@fb.com \
--cc=hasanalmaruf@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=tim.c.chen@linux.intel.com \
--cc=weixugc@google.com \
--cc=yang.shi@linux.alibaba.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).