Vitaly Wool writes:
Existing users, if any, should voice their objections. Otherwise, we can remove z3fold in a few releases.At this point I NACK this patch. We're about to submit an allocator which is clearly better that z3fold and is faster that zsmalloc in most cases and that submission will mark z3fold as deprecated. But for now this move is premature.
Why should that block completely unrelated cleanup work? Let's please not add dependencies between patches when there don't need to be.
