Re: [PATCH v2] z3fold: the 3-fold allocator for compressed pages

[Vitaly Wool]

On Mon, Apr 25, 2016 at 9:28 AM, Vlastimil Babka <vbabka@xxxxxxx> wrote:
> On 04/22/2016 01:22 AM, Andrew Morton wrote:
<snip>
>>
>> So...  why don't we just replace zbud with z3fold?  (Update the changelog
>> to answer this rather obvious question, please!)
>
>
> There was discussion between Seth and Vitaly on v1. Without me knowing the
> details myself, it looked like Seth's objections were addressed, but then
> the thread died. I think there should first be a more clear answer from Seth
> whether z3fold really looks like a clear win (i.e. not workload-dependent)
> over zbud, in which case zbud could be extended?

I have tried to address this question in the changelog for v3 which came out
today. Basically I'd like to play on the safe side and have z3fold
co-existing with
zbud for a while, since zbud is a simple and proven solution which has less
object code and can work without ZPOOL. The original zbud implementation
doesn't use struct page's fields in any way, which z3fold can't get
away without.

As a matter of fact, I don't think there's much of the similar code left between
zbud and z3fold, other than the generic structure.

~vitaly