From: Vlastimil Babka <vbabka@suse.cz>
To: Ananda Badmaev <a.badmaev@clicknet.pro>,
linux-mm@kvack.org, Vitaly Wool <vitaly.wool@konsulko.com>
Subject: Re: [PATCH] mm: add ztree - new allocator for use via zpool API
Date: Thu, 16 Sep 2021 12:12:20 +0200 [thread overview]
Message-ID: <b2fe54ab-ade9-c44c-4ec1-a0dd2e6d4ac9@suse.cz> (raw)
In-Reply-To: <20210916085102.19310-1-a.badmaev@clicknet.pro>
On 9/16/21 10:51, Ananda Badmaev wrote:
> ztree is a versatile backend for zswap and potentially zram. It got its name
> due to the usage of red-black trees to store blocks of compressed objects.
> These blocks consist of several consecutive pages and ztree keeps an integer
> number of objects per block.
>
> For zram, ztree has better worst case malloc() and free() times than zsmalloc,
> does not deteriorate over time and has slightly worse but comparable compression
> ratio. For zswap, ztree has better worst case malloc() and free() times than
> z3fold, better compression ratio than z3fold and supports reclaim unlike zsmalloc.
>
> Signed-off-by: Ananda Badmaev <a.badmaev@clicknet.pro>
So how many of these allocators do we need? Minimally IMHO some data should
be provided for the performance comparison claims above.
Sounds like if this is based on z3fold (I haven't actually compared the
code) and better in every aspect, why not just "upgrade" z3fold to ztree then?
next prev parent reply other threads:[~2021-09-16 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 8:51 Ananda Badmaev
2021-09-16 10:12 ` Vlastimil Babka [this message]
2021-09-16 10:38 ` Vitaly Wool
2021-09-17 4:33 ` Ананда Бадмаев
2021-09-16 9:33 Vitaly Wool
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2fe54ab-ade9-c44c-4ec1-a0dd2e6d4ac9@suse.cz \
--to=vbabka@suse.cz \
--cc=a.badmaev@clicknet.pro \
--cc=linux-mm@kvack.org \
--cc=vitaly.wool@konsulko.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox