On Tue, Jul 30, 2024 at 08:11:16AM +1200, Barry Song wrote: > > We also really need to stop optimizing for this weird zram case and move > > people to zswap instead after fixing the various issues. A special > > block device that isn't really a block device and needs various special > > hooks isn't the right abstraction for different zwap strategies. > > My understanding is zRAM is much more popularly used in embedded > systems than zswap. I seldomly(or never) hear who is using zswap > in Android. it seems pointless to force people to move to zswap, in > embedded systems we don't have a backend real block disk device > after zswap. Well, that is the point. zram is a horrible hack that abuses a block device to implement a feature missing the VM layer. Right now people have a reason for it because zswap requires a "real" backing device and that's fine for them and for now. But instead of building VM infrastructure around these kinds of hacks we need to fix the VM infrastructure. Chris Li has been talking about and working towards a proper swap abstraction and that needs to happen.
