linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Juhyung Park <qkrwngud825@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, Lu Hongfei <luhongfei@vivo.com>,
	Yangtao Li <frank.li@vivo.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: flag as supporting buffered async reads
Date: Tue, 6 Jun 2023 14:40:34 +0800	[thread overview]
Message-ID: <20fb7157-05ae-eeb5-4acd-76b2c82d80b3@kernel.org> (raw)
In-Reply-To: <ZH48E4/AOtk1viOY@google.com>

On 2023/6/6 3:48, Jaegeuk Kim wrote:
> On 05/31, Juhyung Park wrote:
>> Hi Yangtao,
>>
>> I remember hearing that f2fs can perform relatively poorly under io_uring,
>> nice find.
>>
>> I suggest rewriting the commit message though. From the looks of it, it
>> might suggest that FMODE_BUF_RASYNC is a magic flag that automatically
>> improves performance that can be enabled willy nilly.
>>
>> How about something like:
>>
>> f2fs uses generic_file_buffered_read(), which supports buffered async
>> reads since commit 1a0a7853b901 ("mm: support async buffered reads in
>> generic_file_buffered_read()").
> 
> Thanks Juhyung,
> 
> Applied with a minor motification based on yours. :)

The version in dev-test branch looks good to me.

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

> 
>>
>> Match other file-systems and enable it. The read performance has been
>> greatly improved under io_uring:
>>
>>      167M/s -> 234M/s, Increase ratio by 40%
>>
>> Test w/:
>>      ./fio --name=onessd --filename=/data/test/local/io_uring_test
>>      --size=256M --rw=randread --bs=4k --direct=0 --overwrite=0
>>      --numjobs=1 --iodepth=1 --time_based=0 --runtime=10
>>      --ioengine=io_uring --registerfiles --fixedbufs
>>      --gtod_reduce=1 --group_reporting --sqthread_poll=1
>>
>> On Wed, May 31, 2023 at 10:01 PM Yangtao Li via Linux-f2fs-devel
>> <linux-f2fs-devel@lists.sourceforge.net> wrote:
>>>
>>> After enabling this feature, the read performance has been greatly
>>> improved:
>>>
>>>      167M/s -> 234M/s, Increase ratio by 40%
>>>
>>> Test w/:
>>>      ./fio --name=onessd --filename=/data/test/local/io_uring_test
>>>      --size=256M --rw=randread --bs=4k --direct=0 --overwrite=0
>>>      --numjobs=1 --iodepth=1 --time_based=0 --runtime=10
>>>      --ioengine=io_uring --registerfiles --fixedbufs
>>>      --gtod_reduce=1 --group_reporting --sqthread_poll=1
>>>
>>> Signed-off-by: Lu Hongfei <luhongfei@vivo.com>
>>> Signed-off-by: Yangtao Li <frank.li@vivo.com>
>>> ---
>>>   fs/f2fs/file.c | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
>>> index 015ed274dc31..23c68ee946e5 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;
>>> +       filp->f_mode |= FMODE_NOWAIT | FMODE_BUF_RASYNC;
>>>
>>>          return dquot_file_open(inode, filp);
>>>   }
>>> --
>>> 2.39.0
>>>
>>>
>>>
>>> _______________________________________________
>>> Linux-f2fs-devel mailing list
>>> Linux-f2fs-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel


_______________________________________________
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-06  6:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 12:59 [f2fs-dev] [PATCH] f2fs: flag as supporting buffered async reads Yangtao Li via Linux-f2fs-devel
2023-05-31 13:53 ` Juhyung Park
2023-06-05 19:48   ` Jaegeuk Kim
2023-06-06  6:40     ` Chao Yu [this message]
2023-06-07 17:30 ` patchwork-bot+f2fs

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=20fb7157-05ae-eeb5-4acd-76b2c82d80b3@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 \
    --cc=qkrwngud825@gmail.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).