From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, Zhang Yi <yi.zhang@huawei.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
jack@suse.cz, adilger.kernel@dilger.ca, yukuai3@huawei.com
Subject: Re: [PATCH v3 0/4] ext4: improve delalloc buffer write performance
Date: Thu, 9 Sep 2021 10:55:22 -0400 [thread overview]
Message-ID: <163119924594.1572869.9093216296626510411.b4-ty@mit.edu> (raw)
In-Reply-To: <20210716122024.1105856-1-yi.zhang@huawei.com>
On Fri, 16 Jul 2021 20:20:20 +0800, Zhang Yi wrote:
> Changes since v2:
> - Patch 3: fix misleading comment about data truncate in the error path
> of ext4_write_inline_data_end().
>
> Thanks,
> Yi.
>
> [...]
Applied, thanks!
[1/4] ext4: check and update i_disksize properly
commit: 4df031ff5876d94b48dd9ee486ba5522382a06b2
[2/4] ext4: correct the error path of ext4_write_inline_data_end()
commit: 55ce2f649b9e88111270333a8127e23f4f8f42d7
[3/4] ext4: factor out write end code of inline file
commit: 6984aef59814fb5c47b0e30c56e101186b5ebf8c
[4/4] ext4: drop unnecessary journal handle in delalloc write
commit: cc883236b79297f6266ca6f4e7f24f3fd3c736c1
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2021-09-09 14:55 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 ` [PATCH v3 0/4] ext4: improve delalloc buffer write performance Zhang Yi
2021-09-09 14:55 ` Theodore Ts'o [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=163119924594.1572869.9093216296626510411.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=yi.zhang@huawei.com \
--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.