From: Andrew Morton <akpm@linux-foundation.org>
To: Ze Zuo <zuoze1@huawei.com>
Cc: <minchan@kernel.org>, <senozhatsky@chromium.org>,
<axboe@kernel.dk>, <ying.huang@intel.com>,
<aneesh.kumar@linux.ibm.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <linux-block@vger.kernel.org>,
<wangkefeng.wang@huawei.com>
Subject: Re: [PATCH 1/2] zram: add a parameter "node_id" for zram
Date: Sat, 2 Sep 2023 15:55:29 -0700 [thread overview]
Message-ID: <20230902155529.61384b25aae68abb9c262552@linux-foundation.org> (raw)
In-Reply-To: <20230901071942.207010-2-zuoze1@huawei.com>
On Fri, 1 Sep 2023 15:19:41 +0800 Ze Zuo <zuoze1@huawei.com> wrote:
> Add a parameter "node_id" to zram to support storing pages on specific
> node_id node memory.
Please document this in Documentation/admin-guide/blockdev/zram.rst
Should it be a group of nodes rather than a single one? If this
feature is useful, people will want that.
> Now, zram memory allocation is random, however in some cases, specifying
> specific nodes for memory allocation for zram may have good effects. In
> addition, when memory tier is supported, demotion can be achieved not
> only through page migration, it is also possible to apply for memory by
> specifying zram on low-speed device nodes, such as CXL memory devices,
> and compressing pages to these devices through memory reclamation to
> achieve similar effects to migration.
Are any performance testing results available from using this feature?
next prev parent reply other threads:[~2023-09-02 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 7:19 [PATCH 0/2] zram: support for specific numa node " Ze Zuo
2023-09-01 7:19 ` [PATCH 1/2] zram: add a parameter "node_id" " Ze Zuo
2023-09-02 22:55 ` Andrew Morton [this message]
2023-09-05 5:01 ` Sergey Senozhatsky
2023-09-01 7:19 ` [PATCH 2/2] zram: take the benefit of kvzalloc_node Ze Zuo
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=20230902155529.61384b25aae68abb9c262552@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=senozhatsky@chromium.org \
--cc=wangkefeng.wang@huawei.com \
--cc=ying.huang@intel.com \
--cc=zuoze1@huawei.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
all inboxes | Powered by JetHome®