All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Yi <yi.zhang@huawei.com>
To: <tytso@mit.edu>
Cc: <adilger.kernel@dilger.ca>, <jack@suse.cz>, <yukuai3@huawei.com>,
	<linux-ext4@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] ext4: improve delalloc buffer write performance
Date: Sat, 4 Sep 2021 11:21:18 +0800	[thread overview]
Message-ID: <5d0c1cf0-c430-6c15-7cce-dc16bf9d7cf7@huawei.com> (raw)
In-Reply-To: <20210716122024.1105856-1-yi.zhang@huawei.com>

Hi, Ted

Do you plan to merge this speed up patch set for 5.15?

Thanks,
Yi.

On 2021/7/16 20:20, Zhang Yi wrote:
> Hi,
> 
> Changes since v2:
>  - Patch 3: fix misleading comment about data truncate in the error path
>             of ext4_write_inline_data_end().
> 
> Thanks,
> Yi.
> 
> --------
> 
> Changes since v1:
> 
>  - Patch 1: add comments to explain why and how to update i_disksize in
>             ext4_da_write_end().
>  - Patch 3: update i_disksize only if copied is not zero and drop
>             i_size_changed parameter, also drop unused EXT4_STATE_JDATA
>             and i_datasync_tid update code hook.
> 
> Original description:
> 
> This patchset address to improve buffer write performance with delalloc.
> The first patch reduce the unnecessary update i_disksize, the second two
> patch refactor the inline data write procedure and also do some small
> fix, the last patch do improve by remove all unnecessary journal handle
> in the delalloc write procedure.
> 
> After this patch set, we could get a lot of performance improvement.
> Below is the Unixbench comparison data test on my machine with 'Intel
> Xeon Gold 5120' CPU and nvme SSD backend.
> 
> Test cmd:
> 
>   ./Run -c 56 -i 3 fstime fsbuffer fsdisk
> 
> Before this patch set:
> 
>   System Benchmarks Partial Index           BASELINE       RESULT   INDEX
>   File Copy 1024 bufsize 2000 maxblocks       3960.0     422965.0   1068.1
>   File Copy 256 bufsize 500 maxblocks         1655.0     105077.0   634.9
>   File Copy 4096 bufsize 8000 maxblocks       5800.0    1429092.0   2464.0
>                                                                     ========
>   System Benchmarks Index Score (Partial Only)                      1186.6
> 
> After this patch set:
> 
>   System Benchmarks Partial Index           BASELINE       RESULT   INDEX
>   File Copy 1024 bufsize 2000 maxblocks       3960.0     732716.0   1850.3
>   File Copy 256 bufsize 500 maxblocks         1655.0     184940.0   1117.5
>   File Copy 4096 bufsize 8000 maxblocks       5800.0    2427152.0   4184.7
>                                                                     ========
>   System Benchmarks Index Score (Partial Only)                      2053.0
> 
> 
> 
> 
> Zhang Yi (4):
>   ext4: check and update i_disksize properly
>   ext4: correct the error path of ext4_write_inline_data_end()
>   ext4: factor out write end code of inline file
>   ext4: drop unnecessary journal handle in delalloc write
> 
>  fs/ext4/ext4.h   |   3 -
>  fs/ext4/inline.c | 120 ++++++++++++++++++-------------------
>  fs/ext4/inode.c  | 150 ++++++++++++-----------------------------------
>  3 files changed, 99 insertions(+), 174 deletions(-)
> 

  parent reply	other threads:[~2021-09-04  3:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 12:20 [PATCH v3 0/4] ext4: improve delalloc buffer write performance Zhang Yi
2021-07-16 12:20 ` [PATCH v3 1/4] ext4: check and update i_disksize properly Zhang Yi
2021-07-16 12:20 ` [PATCH v3 2/4] ext4: correct the error path of ext4_write_inline_data_end() Zhang Yi
2021-07-16 12:20 ` [PATCH v3 3/4] ext4: factor out write end code of inline file Zhang Yi
2021-07-16 14:57   ` Jan Kara
2021-07-16 12:20 ` [PATCH v3 4/4] ext4: drop unnecessary journal handle in delalloc write Zhang Yi
2021-07-27  5:06   ` [ext4] 57e8668f62: aim7.jobs-per-min 60.2% improvement kernel test robot
2021-07-27  5:06     ` kernel test robot
2021-09-04  3:21 ` Zhang Yi [this message]
2021-09-09 14:55 ` [PATCH v3 0/4] ext4: improve delalloc buffer write performance Theodore Ts'o

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=5d0c1cf0-c430-6c15-7cce-dc16bf9d7cf7@huawei.com \
    --to=yi.zhang@huawei.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=yukuai3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.