| From: |
| Vitaly Wool <vitalywool-AT-gmail.com> |
| To: |
| Linux-MM <linux-mm-AT-kvack.org>, Andrew Morton <akpm-AT-linux-foundation.org>, Dan Streetman <ddstreet-AT-ieee.org>, Minchan Kim <minchan-AT-kernel.org> |
| Subject: |
| [PATCH 0/3] Allow ZRAM to use any zpool-compatible backend |
| Date: |
| Thu, 10 Oct 2019 23:04:14 +0300 |
| Message-ID: |
| <20191010230414.647c29f34665ca26103879c4@gmail.com> |
| Cc: |
| Sergey Senozhatsky <sergey.senozhatsky.work-AT-gmail.com>, LKML <linux-kernel-AT-vger.kernel.org>, Vlastimil Babka <vbabka-AT-suse.cz>, Shakeel Butt <shakeelb-AT-google.com>, Henry Burns <henrywolfeburns-AT-gmail.com>, Theodore Ts'o <tytso-AT-thunk.org> |
| Archive-link: |
| Article |
The coming patchset is a new take on the old issue: ZRAM can currently be used only with zsmalloc even though this may not be the optimal combination for some configurations. The previous (unsuccessful) attempt dates back to 2015 [1] and is notable for the heated discussions it has caused.
The patchset in [1] had basically the only goal of enabling ZRAM/zbud combo which had a very narrow use case. Things have changed substantially since then, and now, with z3fold used widely as a zswap backend, I, as the z3fold maintainer, am getting requests to re-interate on making it possible to use ZRAM with any zpool-compatible backend, first of all z3fold.
The preliminary results for this work have been delivered at Linux Plumbers this year [2]. The talk at LPC, though having attracted limited interest, ended in a consensus to continue the work and pursue the goal of decoupling ZRAM from zsmalloc.
The current patchset has been stress tested on arm64 and x86_64 devices, including the Dell laptop I'm writing this message on now, not to mention several QEmu confugirations.
[1] https://lkml.org/lkml/2015/9/14/356
[2] https://linuxplumbersconf.org/event/4/contributions/551/
