From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, Nanzhe Zhao <nzzhao@126.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/2] f2fs: add 'folio_in_bio' to handle readahead folios with no BIO submission
Date: Fri, 16 Jan 2026 04:33:31 +0000 [thread overview]
Message-ID: <aWm_m0AsbUXcRB6l@google.com> (raw)
In-Reply-To: <aWaPzQ8JXNBdzb4U@casper.infradead.org>
On 01/13, Matthew Wilcox wrote:
> On Sun, Jan 11, 2026 at 06:09:40PM +0800, Nanzhe Zhao wrote:
> > @@ -2545,6 +2548,11 @@ static int f2fs_read_data_large_folio(struct inode *inode,
> > }
> > trace_f2fs_read_folio(folio, DATA);
> > if (rac) {
> > + if (!folio_in_bio) {
> > + if (!ret)
> > + folio_mark_uptodate(folio);
> > + folio_unlock(folio);
>
> folio_end_read(folio, ret == 0);
Thanks.
https://lore.kernel.org/linux-f2fs-devel/20260116043203.2313943-1-jaegeuk@kernel.org/T/#u
>
> surely?
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Nanzhe Zhao <nzzhao@126.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, Chao Yu <chao@kernel.org>
Subject: Re: [f2fs-dev] [PATCH v2 1/2] f2fs: add 'folio_in_bio' to handle readahead folios with no BIO submission
Date: Fri, 16 Jan 2026 04:33:31 +0000 [thread overview]
Message-ID: <aWm_m0AsbUXcRB6l@google.com> (raw)
In-Reply-To: <aWaPzQ8JXNBdzb4U@casper.infradead.org>
On 01/13, Matthew Wilcox wrote:
> On Sun, Jan 11, 2026 at 06:09:40PM +0800, Nanzhe Zhao wrote:
> > @@ -2545,6 +2548,11 @@ static int f2fs_read_data_large_folio(struct inode *inode,
> > }
> > trace_f2fs_read_folio(folio, DATA);
> > if (rac) {
> > + if (!folio_in_bio) {
> > + if (!ret)
> > + folio_mark_uptodate(folio);
> > + folio_unlock(folio);
>
> folio_end_read(folio, ret == 0);
Thanks.
https://lore.kernel.org/linux-f2fs-devel/20260116043203.2313943-1-jaegeuk@kernel.org/T/#u
>
> surely?
next prev parent reply other threads:[~2026-01-16 4:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 10:09 [f2fs-dev] [PATCH v2 0/2] f2fs: fix large folio read corner cases for immutable files Nanzhe Zhao
2026-01-11 10:09 ` Nanzhe Zhao
2026-01-11 10:09 ` [f2fs-dev] [PATCH v2 1/2] f2fs: add 'folio_in_bio' to handle readahead folios with no BIO submission Nanzhe Zhao
2026-01-11 10:09 ` Nanzhe Zhao
2026-01-12 1:02 ` Chao Yu via Linux-f2fs-devel
2026-01-12 1:02 ` Chao Yu
2026-01-12 8:52 ` Nanzhe Zhao
2026-01-12 8:52 ` Nanzhe Zhao
2026-01-12 9:24 ` Chao Yu via Linux-f2fs-devel
2026-01-12 9:24 ` Chao Yu
2026-01-13 17:05 ` Jaegeuk Kim via Linux-f2fs-devel
2026-01-13 17:05 ` Jaegeuk Kim
2026-01-16 3:31 ` Nanzhe Zhao
2026-01-16 3:31 ` Nanzhe Zhao
2026-01-16 8:53 ` Chao Yu via Linux-f2fs-devel
2026-01-16 8:53 ` Chao Yu
2026-01-13 18:32 ` Matthew Wilcox
2026-01-13 18:32 ` Matthew Wilcox
2026-01-16 4:33 ` Jaegeuk Kim via Linux-f2fs-devel [this message]
2026-01-16 4:33 ` Jaegeuk Kim
2026-01-11 10:09 ` [f2fs-dev] [PATCH v2 2/2] f2fs: advance index and offset after zeroing in large folio read Nanzhe Zhao
2026-01-11 10:09 ` Nanzhe Zhao
2026-01-12 1:03 ` Chao Yu via Linux-f2fs-devel
2026-01-12 1:03 ` 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=aWm_m0AsbUXcRB6l@google.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nzzhao@126.com \
--cc=willy@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.