* [PATCH] f2fs: zone: wait for inflight dio completion, excluding pinned files
@ 2025-07-21 5:41 yohan.joung
2025-07-22 3:56 ` Chao Yu
0 siblings, 1 reply; 3+ messages in thread
From: yohan.joung @ 2025-07-21 5:41 UTC (permalink / raw)
To: jaegeuk, chao; +Cc: linux-kernel, linux-f2fs-devel, pilhyun.kim, yohan.joung
pinfile is excluded as it operates with direct I/O
Signed-off-by: yohan.joung <yohan.joung@sk.com>
---
fs/f2fs/file.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 4039ccb5022c..cac8c9650a7a 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -4844,7 +4844,8 @@ static ssize_t f2fs_file_read_iter(struct kiocb *iocb, struct iov_iter *to)
/* In LFS mode, if there is inflight dio, wait for its completion */
if (f2fs_lfs_mode(F2FS_I_SB(inode)) &&
- get_pages(F2FS_I_SB(inode), F2FS_DIO_WRITE))
+ get_pages(F2FS_I_SB(inode), F2FS_DIO_WRITE) &&
+ !f2fs_is_pinned_file(inode))
inode_dio_wait(inode);
if (f2fs_should_use_dio(inode, iocb, to)) {
--
2.33.0
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH] f2fs: zone: wait for inflight dio completion, excluding pinned files
2025-07-21 5:41 [PATCH] f2fs: zone: wait for inflight dio completion, excluding pinned files yohan.joung
@ 2025-07-22 3:56 ` Chao Yu
2025-07-22 4:25 ` [f2fs-dev] " yohan.joung
0 siblings, 1 reply; 3+ messages in thread
From: Chao Yu @ 2025-07-22 3:56 UTC (permalink / raw)
To: yohan.joung, jaegeuk; +Cc: chao, linux-kernel, linux-f2fs-devel, pilhyun.kim
On 7/21/25 13:41, yohan.joung wrote:
> pinfile is excluded as it operates with direct I/O
pinfile can use buffer IO as well?
Thanks,
>
> Signed-off-by: yohan.joung <yohan.joung@sk.com>
> ---
> fs/f2fs/file.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 4039ccb5022c..cac8c9650a7a 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -4844,7 +4844,8 @@ static ssize_t f2fs_file_read_iter(struct kiocb *iocb, struct iov_iter *to)
>
> /* In LFS mode, if there is inflight dio, wait for its completion */
> if (f2fs_lfs_mode(F2FS_I_SB(inode)) &&
> - get_pages(F2FS_I_SB(inode), F2FS_DIO_WRITE))
> + get_pages(F2FS_I_SB(inode), F2FS_DIO_WRITE) &&
> + !f2fs_is_pinned_file(inode))
> inode_dio_wait(inode);
>
> if (f2fs_should_use_dio(inode, iocb, to)) {
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [f2fs-dev] [PATCH] f2fs: zone: wait for inflight dio completion, excluding pinned files
2025-07-22 3:56 ` Chao Yu
@ 2025-07-22 4:25 ` yohan.joung
0 siblings, 0 replies; 3+ messages in thread
From: yohan.joung @ 2025-07-22 4:25 UTC (permalink / raw)
To: linux-f2fs-devel; +Cc: chao, jaegeuk, linux-kernel, pilhyun.kim, yohan.joung
>On 7/21/25 13:41, yohan.joung wrote:
>> pinfile is excluded as it operates with direct I/O
>
>pinfile can use buffer IO as well?
only considered direct I/O. I'll re-upload the pinfile considering buffered I/O
Thanks
>
>Thanks,
>
>>
>> Signed-off-by: yohan.joung <yohan.joung@sk.com>
>> ---
>> fs/f2fs/file.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
>> index 4039ccb5022c..cac8c9650a7a 100644
>> --- a/fs/f2fs/file.c
>> +++ b/fs/f2fs/file.c
>> @@ -4844,7 +4844,8 @@ static ssize_t f2fs_file_read_iter(struct kiocb *iocb, struct iov_iter *to)
>>
>> /* In LFS mode, if there is inflight dio, wait for its completion */
>> if (f2fs_lfs_mode(F2FS_I_SB(inode)) &&
>> - get_pages(F2FS_I_SB(inode), F2FS_DIO_WRITE))
>> + get_pages(F2FS_I_SB(inode), F2FS_DIO_WRITE) &&
>> + !f2fs_is_pinned_file(inode))
>> inode_dio_wait(inode);
>>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-07-22 4:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-07-21 5:41 [PATCH] f2fs: zone: wait for inflight dio completion, excluding pinned files yohan.joung
2025-07-22 3:56 ` Chao Yu
2025-07-22 4:25 ` [f2fs-dev] " yohan.joung
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®