mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Nanzhe Zhao <nzzhao.sigma@gmail.com>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	Barry Song <baohua@kernel.org>, Juan Yescas <jyescas@google.com>,
	Pengfei Li <lipengfei28@xiaomi.com>, Dev Jain <Dev.Jain@arm.com>,
	linux-kernel@vger.kernel.org,
	David Hildenbrand <David.Hildenbrand@arm.com>,
	Bo Zhang <zhangbo56@xiaomi.com>,
	Kalesh Singh <kaleshsingh@google.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Ryan Roberts <Ryan.Roberts@arm.com>
Subject: Re: [f2fs-dev] [PATCH 03/14] f2fs: support regular file buffered writes
Date: Wed, 9 Sep 2026 16:41:37 +0800	[thread overview]
Message-ID: <01e67f12-f759-492a-a332-3c9d5d4c7fdf@kernel.org> (raw)
In-Reply-To: <20260907130313.2626386-1-zhaonanzhe@xiaomi.com>

On 9/7/26 21:03, Nanzhe Zhao wrote:
> On Thu, 27 Aug 2026 16:56:53 +0800, Chao Yu wrote:
>> +	/* Wait for pending drops back to bias which indicates all bio have completed. */
>> +	while (READ_ONCE(ffs->read_pages_pending) != 1)
>> +		f2fs_io_schedule_timeout(DEFAULT_SCHEDULE_TIMEOUT);
>>
>> Suspect there will be potential performance issue, as timeout interval
>> is large.
>>
>> Looks hacky.
> 
> Thanks for the review.
> 
> Maybe we can switch this to an event-driven wait instead:
> 
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ includes
>  	#include <linux/fiemap.h>
> +	#include <linux/wait_bit.h>	/* wait_var_event_io / wake_up_var */
>  	#include <linux/iomap.h>
> @@ f2fs_submit_page_read_sync()
> -	/* Wait for pending drops back to bias which indicates all bio have completed. */
> -	while (READ_ONCE(ffs->read_pages_pending) != 1)
> -		f2fs_io_schedule_timeout(DEFAULT_SCHEDULE_TIMEOUT);
> +	/* Wait until all bios have completed (pending drops back to our bias). */
> +	wait_var_event_io(&ffs->read_pages_pending,
> +			  READ_ONCE(ffs->read_pages_pending) == 1);
> @@ f2fs_finish_read_bio()
>  			ffs->read_pages_pending -= nr_pages;
>  			finished = !ffs->read_pages_pending;
>  			spin_unlock_irqrestore(&ffs->state_lock, flags);
> +
> +			/* Wake f2fs_submit_page_read_sync() waiters (if any). */
> +			wake_up_var(&ffs->read_pages_pending);
>  		}
> 
> However, this requires an extra wake_up_var(&ffs->read_pages_pending)
> in f2fs_finish_read_bio(). I'm not sure whether adding an extra
> wake-up in the completion callback is a good practice - what do you
> think?

Sure, IMO, stability has higher priority, we can tune this later if it
takes much time.

Thanks,

> 
> Thanks,
> Nanzhe


  reply	other threads:[~2026-09-09  8:41 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26  8:26 [PATCH 00/14] f2fs: support & optimize large folios for writable files Nanzhe Zhao
2026-08-26  8:26 ` [PATCH 01/14] f2fs: extend folio state for large folio write path Nanzhe Zhao
2026-08-27  6:57   ` Chao Yu
2026-08-27 20:51     ` [f2fs-dev] " Daeho Jeong
2026-09-04  3:44       ` Daeho Jeong
2026-09-07  6:49       ` Nanzhe Zhao
2026-09-07  9:31       ` Nanzhe Zhao
2026-09-09 20:25         ` Daeho Jeong
2026-09-08  3:41       ` Nanzhe Zhao
2026-08-26  8:26 ` [PATCH 02/14] f2fs: carry subpage offset and count in write IO Nanzhe Zhao
2026-08-27  7:16   ` Chao Yu
2026-08-27 21:06     ` [f2fs-dev] " Daeho Jeong
2026-08-26  8:26 ` [PATCH 03/14] f2fs: support regular file buffered writes on large folios Nanzhe Zhao
2026-08-27  8:56   ` Chao Yu
2026-08-27 21:13     ` [f2fs-dev] " Daeho Jeong
2026-09-07  3:51     ` [f2fs-dev] [PATCH 03/14] f2fs: support regular file buffered writes Nanzhe Zhao
2026-09-07  6:59       ` Chao Yu
2026-09-07 11:58     ` Nanzhe Zhao
2026-09-07 13:03     ` Nanzhe Zhao
2026-09-09  8:41       ` Chao Yu [this message]
2026-09-09 20:40     ` [f2fs-dev] [PATCH 03/14] f2fs: support regular file buffered writes on large folios Daeho Jeong
2026-09-10 10:33       ` Nanzhe Zhao
2026-08-31  3:04   ` Chao Yu
2026-08-26  8:26 ` [PATCH 04/14] f2fs: support atomic file large folios buffered write Nanzhe Zhao
2026-08-27  9:24   ` Chao Yu
2026-08-26  8:26 ` [PATCH 05/14] f2fs: support large folio writeback Nanzhe Zhao
2026-08-27 11:17   ` Chao Yu
2026-08-27 22:39     ` [f2fs-dev] " Daeho Jeong
2026-09-04  4:04       ` Daeho Jeong
2026-09-04  4:07         ` Daeho Jeong
2026-09-07  3:57         ` Nanzhe Zhao
2026-09-09 21:03           ` Daeho Jeong
2026-09-07 10:12       ` Nanzhe Zhao
2026-09-09 21:08         ` Daeho Jeong
2026-09-07  3:51     ` Nanzhe Zhao
2026-09-07  6:59       ` Chao Yu
2026-08-26  8:26 ` [PATCH 06/14] f2fs: prepare mmap write faults for large folios Nanzhe Zhao
2026-08-27 12:36   ` Chao Yu
2026-08-28 17:18     ` [f2fs-dev] " Daeho Jeong
2026-09-07  7:34     ` Nanzhe Zhao
2026-09-09  7:34       ` Chao Yu
2026-09-09 21:22         ` Daeho Jeong
2026-08-26  8:26 ` [PATCH 07/14] f2fs: make GC migration large-folio aware Nanzhe Zhao
2026-08-28 17:20   ` [f2fs-dev] " Daeho Jeong
2026-09-07 11:45     ` Nanzhe Zhao
2026-09-09 19:33       ` Daeho Jeong
2026-08-31  3:14   ` Chao Yu
2026-08-26  8:26 ` [PATCH 08/14] f2fs: optimize small block size large folio read Nanzhe Zhao
2026-08-31  4:21   ` Chao Yu
2026-08-26  8:26 ` [PATCH 09/14] f2fs: support partial uptodate " Nanzhe Zhao
2026-08-26  8:26 ` [PATCH 10/14] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao
2026-08-31  7:46   ` Chao Yu
2026-08-26 13:09 ` [PATCH 11/14] f2fs: fix zeroing paths for large folios Nanzhe Zhao
2026-08-31  7:56   ` Chao Yu
2026-08-26 13:09 ` [PATCH 12/14] f2fs: handle block cloning within the same large folio Nanzhe Zhao
2026-08-31  8:19   ` Chao Yu
2026-09-07  9:57     ` [f2fs-dev] " Nanzhe Zhao
2026-09-07 10:24       ` Chao Yu
2026-08-26 13:09 ` [PATCH 13/14] f2fs: allow large folio support to writeable files Nanzhe Zhao
2026-08-28 17:44   ` [f2fs-dev] " Daeho Jeong
2026-09-07  6:33     ` Nanzhe Zhao
2026-09-09 19:23       ` Daeho Jeong
2026-08-31  8:31   ` Chao Yu
2026-09-07 11:14     ` [f2fs-dev] " Nanzhe Zhao
2026-08-26 13:09 ` [PATCH 14/14] f2fs: make compressed files compatible with large folio Nanzhe Zhao
2026-08-28 17:52   ` [f2fs-dev] " Daeho Jeong
2026-09-07  3:45     ` Nanzhe Zhao
2026-08-31  8:46   ` 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=01e67f12-f759-492a-a332-3c9d5d4c7fdf@kernel.org \
    --to=chao@kernel.org \
    --cc=David.Hildenbrand@arm.com \
    --cc=Dev.Jain@arm.com \
    --cc=Ryan.Roberts@arm.com \
    --cc=baohua@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=jyescas@google.com \
    --cc=kaleshsingh@google.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lipengfei28@xiaomi.com \
    --cc=nzzhao.sigma@gmail.com \
    --cc=zhangbo56@xiaomi.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

all inboxes | Powered by JetHome®