From: Liu Shixin <liushixin2@huawei.com>
To: Seth Jennings <sjenning@redhat.com>,
Dan Streetman <ddstreet@ieee.org>,
Vitaly Wool <vitaly.wool@konsulko.com>,
Andrew Morton <akpm@linux-foundation.org>,
Nathan Chancellor <nathan@kernel.org>,
"Christoph Hellwig" <hch@lst.de>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Liu Shixin <liushixin2@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH v5 0/5] Delay the initializaton of zswap
Date: Thu, 15 Sep 2022 11:49:58 +0800 [thread overview]
Message-ID: <20220915035003.3347466-1-liushixin2@huawei.com> (raw)
In the initialization of zswap, about 18MB memory will be allocated for
zswap_pool. Since not all users use zswap, the memory may be wasted. Save
the memory for these users by delaying the initialization of zswap to
first enablement.
v4->v5: Rebase on next-20220913, the previous first patch is superseded
by patch ("frontswap: don't call ->init if no ops are registered").
v3->v4: Revert three patches to replace previous patch[1-2] suggested by
Vitaly.
v2->v3: Fix frontswap_ops NULL reported by Nathan and add init for online
swap device in backend register.
v1->v2: Change init_zswap to zswap_init suggested by Andrew.
Liu Shixin (5):
Revert "mm: mark swap_lock and swap_active_head static"
Revert "frontswap: simplify frontswap_register_ops"
mm/zswap: replace zswap_init_{started/failed} with zswap_init_state
mm/zswap: delay the initializaton of zswap until the first enablement
mm/zswap: skip confusing print info
include/linux/swapfile.h | 2 ++
mm/frontswap.c | 42 ++++++++++++++++++++++
mm/swapfile.c | 4 +--
mm/zswap.c | 77 ++++++++++++++++++++++++++++++----------
4 files changed, 104 insertions(+), 21 deletions(-)
--
2.25.1
next reply other threads:[~2022-09-15 3:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 3:49 Liu Shixin [this message]
2022-09-15 3:49 ` [PATCH v5 1/5] Revert "mm: mark swap_lock and swap_active_head static" Liu Shixin
2022-09-15 3:50 ` [PATCH v5 2/5] Revert "frontswap: simplify frontswap_register_ops" Liu Shixin
2022-09-20 12:13 ` Christoph Hellwig
2022-09-21 1:42 ` Liu Shixin
2022-09-27 7:27 ` Christoph Hellwig
2022-09-27 11:12 ` Liu Shixin
2022-09-27 12:31 ` Christoph Hellwig
2022-09-15 3:50 ` [PATCH v5 3/5] mm/zswap: replace zswap_init_{started/failed} with zswap_init_state Liu Shixin
2022-09-15 3:50 ` [PATCH v5 4/5] mm/zswap: delay the initializaton of zswap until the first enablement Liu Shixin
2022-09-15 3:50 ` [PATCH v5 5/5] mm/zswap: skip confusing print info Liu Shixin
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=20220915035003.3347466-1-liushixin2@huawei.com \
--to=liushixin2@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nathan@kernel.org \
--cc=sjenning@redhat.com \
--cc=vitaly.wool@konsulko.com \
--cc=wangkefeng.wang@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