[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d652n6zrqbkt4oltusd5egbnrvd5xz3k4kbmqnfuwuatdyuekn@22jscte4mx7m>
Date: Sun, 23 Nov 2025 09:22:48 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Gao Xiang <hsiangkao@...ux.alibaba.com>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
Yuwen Chen <ywen.chen@...mail.com>, akpm@...ux-foundation.org, bgeffon@...gle.com,
licayy@...look.com, linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, minchan@...nel.org, richardycc@...gle.com
Subject: Re: [RFC PATCHv5 0/6] zram: introduce writeback bio batching
On (25/11/22 20:24), Gao Xiang wrote:
> >
> > > zram(ext4) -> backing ext4/btrfs
> >
> > This is not a valid configuration, as far as I'm concerned.
> > Unless I'm missing your point.
>
> Why it's not valid? zram can be used as a regular virtual
> block device, and format with any fs, and mount the zram
> then.
If you want to move data between two filesystems, then just
mount both devices and cp/mv data between them. zram is not
going to do that for you, zram writeback is for different
purpose.
Powered by blists - more mailing lists