linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Yangtao Li <frank.li@vivo.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, Lu Hongfei <luhongfei@vivo.com>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: enable nowait async buffered writes
Date: Thu, 8 Jun 2023 17:38:07 +0800	[thread overview]
Message-ID: <059b17ce-cb65-fd55-29b1-2b253c6b41c4@kernel.org> (raw)
In-Reply-To: <29bea47b-9085-05e7-d254-a40007e6c7f3@vivo.com>

On 2023/6/6 19:13, Yangtao Li wrote:
> On 2023/6/6 14:43, Chao Yu wrote:
> 
>> On 2023/5/31 22:40, Yangtao Li wrote:
>>> This adds the async buffered write support to f2fs,
>>> the following is the relevant test data.
>>
>> Yangtao,
>>
>> Could you please provide detailed test command?
> 
> 
> Use fio to test, the following is the configuration:
> 
> # io_uring
> [global]
> ioengine=io_uring
> sqthread_poll=1
> threads=1
> iodepth=32
> hipri=0
> direct=0
> fixedbufs=0
> uncached=0
> nowait=0
> force_async=0
> randrepeat=0
> time_based=0
> size=256M
> filename=/data/test/local/io_uring_test
> group_reporting
> [read256B-rand]
> bs=4096
> rw=randwrite
> numjobs=1

Thanks, it looks the performance is not very stable when iodepth is
large, e.g. 32.

Could you please add above test parameter into commit message?

Otherwise, this patch looks good to me.

Thanks,

> 
> 
>>
>> Thanks,
>>
>>>
>>> iodepth      | 1    | 2    | 4    | 8    | 16   |
>>> before(M/s)  | 1012 | 1133 | 894  | 981  | 866  |
>>> after(M/s)   | 1488 | 1896 | 2081 | 2188 | 2207 |
>>>
>>> Signed-off-by: Lu Hongfei <luhongfei@vivo.com>
>>> Signed-off-by: Yangtao Li <frank.li@vivo.com>
>>> ---
>>>   fs/f2fs/file.c | 5 +----
>>>   1 file changed, 1 insertion(+), 4 deletions(-)
>>>
>>> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
>>> index 23c68ee946e5..4faf2c04e325 100644
>>> --- a/fs/f2fs/file.c
>>> +++ b/fs/f2fs/file.c
>>> @@ -546,7 +546,7 @@ static int f2fs_file_open(struct inode *inode, struct file *filp)
>>>       if (err)
>>>           return err;
>>>   -    filp->f_mode |= FMODE_NOWAIT | FMODE_BUF_RASYNC;
>>> +    filp->f_mode |= FMODE_NOWAIT | FMODE_BUF_RASYNC | FMODE_BUF_WASYNC;
>>>         return dquot_file_open(inode, filp);
>>>   }
>>> @@ -4515,9 +4515,6 @@ static ssize_t f2fs_buffered_write_iter(struct kiocb *iocb,
>>>       struct inode *inode = file_inode(file);
>>>       ssize_t ret;
>>>   -    if (iocb->ki_flags & IOCB_NOWAIT)
>>> -        return -EOPNOTSUPP;
>>> -
>>>       current->backing_dev_info = inode_to_bdi(inode);
>>>       ret = generic_perform_write(iocb, from);
>>>       current->backing_dev_info = NULL;


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2023-06-08  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 14:40 [f2fs-dev] [PATCH] f2fs: enable nowait async buffered writes Yangtao Li via Linux-f2fs-devel
2023-06-06  6:43 ` Chao Yu
2023-06-06 11:13   ` Yangtao Li via Linux-f2fs-devel
2023-06-08  9:38     ` Chao Yu [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=059b17ce-cb65-fd55-29b1-2b253c6b41c4@kernel.org \
    --to=chao@kernel.org \
    --cc=frank.li@vivo.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luhongfei@vivo.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).