linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Wool <vitaly.wool@konsulko.com>
To: linux-mm@kvack.org
Cc: Vitaly Wool <vitaly.wool@konsulko.com>
Subject: Re: [PATCH v2] mm: add ztree - new allocator for use via zpool API
Date: Wed,  2 Mar 2022 14:14:35 +0200	[thread overview]
Message-ID: <20220302121434.760753-1-vitaly.wool@konsulko.com> (raw)
In-Reply-To: <20220301092503.44444-1-a.badmaev@clicknet.pro>

>     Ztree stores integer number of compressed objects per ztree block. These
> blocks consist of several physical pages (from 1 to 8) and are arranged in trees.
>     The range from 0 to PAGE_SIZE is divided into the number of intervals
> corresponding to the number of trees and each tree only operates objects of size
> from its interval. Thus the block trees are isolated from each other, which makes it
> possible to simultaneously perform actions with several objects from different trees.
>     Blocks make it possible to densely arrange objects of various sizes resulting in
> low internal fragmentation. Also this allocator tries to fill incomplete blocks
> instead of adding new ones thus in many cases providing a compression ratio
> substantially higher than z3fold and zbud.
>     Apart from greater flexibility, ztree is significantly superior to other zpool
> backends with regard to the worst execution times, thus allowing for better response
> time and real-time characteristics of the whole system.
> 
> Signed-off-by: Ananda Badmaev <a.badmaev@clicknet.pro>

Signed-off-by: Vitaly Wool <vitaly.wool@konsulko.com>



      reply	other threads:[~2022-03-02 12:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  9:25 Ananda
2022-03-02 12:14 ` Vitaly Wool [this message]

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=20220302121434.760753-1-vitaly.wool@konsulko.com \
    --to=vitaly.wool@konsulko.com \
    --cc=linux-mm@kvack.org \
    /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