linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: linux-erofs@lists.ozlabs.org
Subject: [PATCH v7 0/3] erofs-utils: optimize buffer allocation logic
Date: Sat, 23 Jan 2021 01:11:50 +0800	[thread overview]
Message-ID: <20210122171153.27404-1-hsiangkao@aol.com> (raw)
In-Reply-To: 20210122171153.27404-1-hsiangkao.ref@aol.com

Hi all,

This introduces bucket lists for mapped buffer block to boost up
buffer allocation and buffer mapping. Thanks to Weiwen for
contribution!

changes since v6:
 - introduce erofs_bfind_for_attach to clean up erofs_balloc();
 - use a new formula mentioned by Jianan to calculate used_before;
 - only DBG_BUGON on debug version for __erofs_battach < 0.

Thanks,
Gao Xiang  

Gao Xiang (1):
  erofs-utils: introduce erofs_bfind_for_attach()

Hu Weiwen (2):
  erofs-utils: get rid of `end' argument from erofs_mapbh()
  erofs-utils: optimize buffer allocation logic

 include/erofs/cache.h |   3 +-
 lib/cache.c           | 186 ++++++++++++++++++++++++++++++++----------
 lib/compress.c        |   2 +-
 lib/inode.c           |  10 +--
 lib/xattr.c           |   2 +-
 mkfs/main.c           |   2 +-
 6 files changed, 151 insertions(+), 54 deletions(-)

-- 
2.24.0


       reply	other threads:[~2021-01-22 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210122171153.27404-1-hsiangkao.ref@aol.com>
2021-01-22 17:11 ` Gao Xiang via Linux-erofs [this message]
2021-01-22 17:11   ` [PATCH v7 1/3] erofs-utils: get rid of `end' argument from erofs_mapbh() Gao Xiang via Linux-erofs
2021-02-06 15:28     ` Li GuiFu via Linux-erofs
2021-01-22 17:11   ` [PATCH v7 2/3] erofs-utils: introduce erofs_bfind_for_attach() Gao Xiang via Linux-erofs
2021-02-06 15:29     ` Li GuiFu via Linux-erofs
2021-01-22 17:11   ` [PATCH v7 3/3] erofs-utils: optimize buffer allocation logic Gao Xiang via Linux-erofs
2021-02-06 15:29     ` Li GuiFu via Linux-erofs

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=20210122171153.27404-1-hsiangkao@aol.com \
    --to=linux-erofs@lists.ozlabs.org \
    --cc=hsiangkao@aol.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;
as well as URLs for NNTP newsgroup(s).