All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yosry Ahmed <yosryahmed@google.com>
To: mengfanhui <mengfanhui@kylinos.cn>
Cc: tsbogend@alpha.franken.de, geert+renesas@glider.be,
	 linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org,  hannes@cmpxchg.org, nphamcs@gmail.com,
	chengming.zhou@linux.dev
Subject: Re: [PATCH] config/mips: support zswap function
Date: Wed, 20 Mar 2024 07:28:24 +0000	[thread overview]
Message-ID: <ZfqQGGfKStVxDwYT@google.com> (raw)
In-Reply-To: <021efce7-1e40-43a6-9bfd-0d968bfcd5a8@kylinos.cn>

On Wed, Mar 20, 2024 at 02:44:21PM +0800, mengfanhui wrote:
> Zswap and zsmalloc are compression methods, and kernel configuration can be configured simultaneously.
> zbud is an algorithm, and users can use that method if they want to use it.It won't affect each other.

Zswap compressed swapped out pages in-memory. To store those compressed
pages, it uses one of three allocators that implement the zpool API:
zbud, z3fold, and zsmalloc. In that sense, zsmalloc is comparable to
zbud, not zswap. I suspect you are mixing up zsmalloc and zram.

Anyway, zsmalloc is the default allocator and should be better for
almost all use cases. So unless you have a very good reason to use zbud
over zsmalloc, please do not use zbud. We are trying to deprecate zbud
and z3fold.

> 
> 在 2024/3/20 14:00, Yosry Ahmed 写道:
> > On Fri, Jan 26, 2024 at 03:55:47PM +0800, mengfanhui wrote:
> >> Solution /sys/module/zswap/parameters/enabled attribute node
> >> does not exist issue,handle zpool zbud initialization failed,
> >> open CONFIG_ZSWAP CONFIG_ZPOOL CONFIG_ZBUD configuration,manual
> >> zswap function by /sys/module/zswap/parameters/enabled file
> >>
> >> Signed-off-by: mengfanhui <mengfanhui@kylinos.cn>
> >> ---
> >>  arch/mips/configs/generic_defconfig | 3 +++
> >>  1 file changed, 3 insertions(+)
> >>
> >> diff --git a/arch/mips/configs/generic_defconfig b/arch/mips/configs/generic_defconfig
> >> index 071e2205c7ed..14884df392f4 100644
> >> --- a/arch/mips/configs/generic_defconfig
> >> +++ b/arch/mips/configs/generic_defconfig
> >> @@ -13,6 +13,9 @@ CONFIG_CGROUP_DEVICE=y
> >>  CONFIG_CGROUP_CPUACCT=y
> >>  CONFIG_NAMESPACES=y
> >>  CONFIG_USER_NS=y
> >> +CONFIG_ZSWAP=y
> >> +CONFIG_ZPOOL=y
> >> +CONFIG_ZBUD=y
> > 
> > Any reason for choosing zbud over zsmalloc, the default zswap allocator?
> > 
> >>  CONFIG_SCHED_AUTOGROUP=y
> >>  CONFIG_BLK_DEV_INITRD=y
> >>  CONFIG_BPF_SYSCALL=y
> >> -- 
> >> 2.25.1
> >>

  reply	other threads:[~2024-03-20  7:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26  7:55 [PATCH] config/mips: support zswap function mengfanhui
2024-03-20  2:00 ` mengfanhui
2024-03-24  9:37   ` Thomas Bogendoerfer
2024-03-20  6:00 ` Yosry Ahmed
2024-03-20  6:44   ` mengfanhui
2024-03-20  7:28     ` Yosry Ahmed [this message]
2024-03-20  6:59   ` mengfanhui

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=ZfqQGGfKStVxDwYT@google.com \
    --to=yosryahmed@google.com \
    --cc=chengming.zhou@linux.dev \
    --cc=geert+renesas@glider.be \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mengfanhui@kylinos.cn \
    --cc=nphamcs@gmail.com \
    --cc=tsbogend@alpha.franken.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.