> We only keep pages that compress to PAGE_SIZE/2 or less. Compressed > chunks are > stored using xvmalloc memory allocator which is already being used by > zram > driver for the same purpose. Zero-filled pages are checked and no > memory is > allocated for them. I'm curious about this policy choice. I can see why one would want to ensure that the average page is compressed to less than PAGE_SIZE/2, and preferably PAGE_SIZE/2 minus the overhead of the data structures necessary to track the page. And I see that this makes no difference when the reclamation algorithm is random (as it is for now). But once there is some better reclamation logic, I'd hope that this compression factor restriction would be lifted and replaced with something much higher. IIRC, compression is much more expensive than decompression so there's no CPU-overhead argument here either, correct? Thanks, Dan -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href