From: <changfengnan@vivo.com>
To: "'Gao Xiang'" <hsiangkao@redhat.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] 答复: [PATCH] f2fs: compress: avoid unnecessary check in f2fs_prepare_compress_overwrite
Date: Mon, 26 Apr 2021 16:42:20 +0800 [thread overview]
Message-ID: <004c01d73a78$12f23a30$38d6ae90$@vivo.com> (raw)
In-Reply-To: <20210426031902.GA3934275@xiangao.remote.csb>
Thank you for the reminder, I hadn't thought about fallocate before.
I have done some tests and the results are as expected.
Here is my test method, create a compressed file, and use fallocate with keep size, when write data to expand area, f2fs_prepare_compress_overwrite
always return 0, the behavior is same as my patch , apply my patch can avoid those check.
Is there anything else I haven't thought of?
-----邮件原件-----
发件人: Gao Xiang <hsiangkao@redhat.com>
发送时间: 2021年4月26日 11:19
收件人: Fengnan Chang <changfengnan@vivo.com>
抄送: chao@kernel.org; jaegeuk@kernel.org;
linux-f2fs-devel@lists.sourceforge.net
主题: Re: [f2fs-dev] [PATCH] f2fs: compress: avoid unnecessary check in
f2fs_prepare_compress_overwrite
On Mon, Apr 26, 2021 at 10:11:53AM +0800, Fengnan Chang wrote:
> when write compressed file with O_TRUNC, there will be a lot of
> unnecessary check valid blocks in f2fs_prepare_compress_overwrite,
> especially when written in page size, remove it.
>
> Signed-off-by: Fengnan Chang <changfengnan@vivo.com>
Even though I didn't look into the whole thing, my reaction here is roughly
how to handle fallocate with keep size? Does it work as expected?
> ---
> fs/f2fs/data.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c index
> cf935474ffba..9c3b0849f35e 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -3270,6 +3270,7 @@ static int f2fs_write_begin(struct file *file,
> struct address_space *mapping,
> struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
> struct page *page = NULL;
> pgoff_t index = ((unsigned long long) pos) >> PAGE_SHIFT;
> + pgoff_t end = (i_size_read(inode) + PAGE_SIZE - 1) >> PAGE_SHIFT;
> bool need_balance = false, drop_atomic = false;
> block_t blkaddr = NULL_ADDR;
> int err = 0;
> @@ -3306,6 +3307,9 @@ static int f2fs_write_begin(struct file *file,
> struct address_space *mapping,
>
> *fsdata = NULL;
>
> + if (index >= end)
> + goto repeat;
> +
> ret = f2fs_prepare_compress_overwrite(inode, pagep,
> index, fsdata);
> if (ret < 0) {
> --
> 2.29.0
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-04-26 8:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 2:11 [f2fs-dev] [PATCH] f2fs: compress: avoid unnecessary check in f2fs_prepare_compress_overwrite Fengnan Chang
2021-04-26 3:19 ` Gao Xiang
2021-04-26 8:42 ` changfengnan [this message]
2021-04-26 9:00 ` [f2fs-dev] 答复: " Gao Xiang
2021-04-26 12:16 ` [f2fs-dev] 答复: " changfengnan
2021-05-06 9:15 ` [f2fs-dev] " Chao Yu
2021-05-06 9:58 ` Gao Xiang via Linux-f2fs-devel
2021-05-06 10:37 ` Chao Yu
2021-05-06 12:15 ` Gao Xiang via Linux-f2fs-devel
2021-05-06 12:15 ` [f2fs-dev] 答复: " changfengnan
2021-05-06 12:38 ` Gao Xiang via Linux-f2fs-devel
2021-04-27 12:42 ` [f2fs-dev] " Chao Yu
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='004c01d73a78$12f23a30$38d6ae90$@vivo.com' \
--to=changfengnan@vivo.com \
--cc=hsiangkao@redhat.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).