linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hu Weiwen <sehuww@mail.scut.edu.cn>
To: Gao Xiang <hsiangkao@redhat.com>,
	Li Guifu <bluce.liguifu@huawei.com>,
	Miao Xie <miaoxie@huawei.com>, Fang Wei <fangwei1@huawei.com>
Cc: Hu Weiwen <sehuww@mail.scut.edu.cn>, linux-erofs@lists.ozlabs.org
Subject: [PATCH v2 0/2] Optimize mkfs to O(N), N = #files
Date: Sat,  9 Jan 2021 16:28:08 +0800	[thread overview]
Message-ID: <20210109082810.32169-1-sehuww@mail.scut.edu.cn> (raw)
In-Reply-To: <20210108181545.GA613131@xiangao.remote.csb>

Hi Xiang,

Thanks for your review.

Integrating the list_head to struct erofs_buffer_block seems better. And I removed the extra braces.

My previous patches were sent by "git send-email", but unfortunately, Outlook changed my Message-ID, so they did not appear in one thread. Sorry for that, I will try another email provider this time.

Hu Weiwen (2):
  erofs-utils: optimize mkfs to O(N), N = #files
  erofs-utils: refactor: remove end argument from erofs_mapbh

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

--
2.17.1


  reply	other threads:[~2021-01-09  8:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-01  9:11 [PATCH 1/2] erofs-utils: optimize mkfs to O(N), N = #files 胡玮文
2021-01-01  9:50 ` 胡 玮文
2021-01-02  5:09   ` Gao Xiang
2021-01-08 18:15 ` Gao Xiang
2021-01-09  8:28   ` Hu Weiwen [this message]
2021-01-09  8:28     ` [PATCH v2 " Hu Weiwen
2021-01-09  8:28     ` [PATCH v2 2/2] erofs-utils: refactor: remove end argument from erofs_mapbh Hu Weiwen

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=20210109082810.32169-1-sehuww@mail.scut.edu.cn \
    --to=sehuww@mail.scut.edu.cn \
    --cc=bluce.liguifu@huawei.com \
    --cc=fangwei1@huawei.com \
    --cc=hsiangkao@redhat.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=miaoxie@huawei.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).