From: Joanne Koong <joannelkoong@gmail.com>
To: miklos@szeredi.hu, linux-fsdevel@vger.kernel.org
Cc: josef@toxicpanda.com, bernd.schubert@fastmail.fm,
jefflexu@linux.alibaba.com, willy@infradead.org,
shakeel.butt@linux.dev, kernel-team@meta.com
Subject: [PATCH 05/12] fuse: support large folios for folio reads
Date: Fri, 8 Nov 2024 16:12:51 -0800 [thread overview]
Message-ID: <20241109001258.2216604-6-joannelkoong@gmail.com> (raw)
In-Reply-To: <20241109001258.2216604-1-joannelkoong@gmail.com>
Add support for folios larger than one page size for folio reads into
the page cache.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
---
fs/fuse/file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index 6ee23ab9b7f2..399bc8898cc4 100644
--- a/fs/fuse/file.c
+++ b/fs/fuse/file.c
@@ -797,7 +797,7 @@ static int fuse_do_readfolio(struct file *file, struct folio *folio)
struct inode *inode = folio->mapping->host;
struct fuse_mount *fm = get_fuse_mount(inode);
loff_t pos = folio_pos(folio);
- struct fuse_folio_desc desc = { .length = PAGE_SIZE };
+ struct fuse_folio_desc desc = { .length = folio_size(folio) };
struct fuse_io_args ia = {
.ap.args.page_zeroing = true,
.ap.args.out_pages = true,
--
2.43.5
next prev parent reply other threads:[~2024-11-09 0:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 0:12 [PATCH 00/12] fuse: support large folios Joanne Koong
2024-11-09 0:12 ` [PATCH 01/12] fuse: support copying " Joanne Koong
2024-11-21 22:27 ` Josef Bacik
2024-11-09 0:12 ` [PATCH 02/12] fuse: support large folios for retrieves Joanne Koong
2024-11-21 22:28 ` Josef Bacik
2024-11-09 0:12 ` [PATCH 03/12] fuse: refactor fuse_fill_write_pages() Joanne Koong
2024-11-21 22:28 ` Josef Bacik
2024-11-09 0:12 ` [PATCH 04/12] fuse: support large folios for non-writeback writes Joanne Koong
2024-11-12 17:32 ` Joanne Koong
2024-11-13 18:41 ` Joanne Koong
2024-11-21 22:32 ` Josef Bacik
2024-11-09 0:12 ` Joanne Koong [this message]
2024-11-22 14:42 ` [PATCH 05/12] fuse: support large folios for folio reads Josef Bacik
2024-11-09 0:12 ` [PATCH 06/12] fuse: support large folios for symlinks Joanne Koong
2024-11-22 14:43 ` Josef Bacik
2024-11-09 0:12 ` [PATCH 07/12] fuse: support large folios for stores Joanne Koong
2024-11-22 14:45 ` Josef Bacik
2024-11-09 0:12 ` [PATCH 08/12] fuse: support large folios for queued writes Joanne Koong
2024-11-22 14:45 ` Josef Bacik
2024-11-09 0:12 ` [PATCH 09/12] fuse: support large folios for readahead Joanne Koong
2024-11-22 14:47 ` Josef Bacik
2024-11-25 19:23 ` Joanne Koong
2024-11-09 0:12 ` [PATCH 10/12] fuse: support large folios for direct io Joanne Koong
2024-11-22 14:49 ` Josef Bacik
2024-11-09 0:12 ` [PATCH 11/12] fuse: support large folios for writeback Joanne Koong
2024-11-22 14:50 ` Josef Bacik
2024-11-09 0:12 ` [PATCH 12/12] fuse: enable large folios Joanne Koong
2024-11-22 14:51 ` Josef Bacik
2024-11-09 0:22 ` [PATCH 00/12] fuse: support " Joanne Koong
2024-11-09 0:32 ` Bernd Schubert
2024-11-11 17:44 ` Joanne Koong
2024-11-13 18:58 ` Joanne Koong
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=20241109001258.2216604-6-joannelkoong@gmail.com \
--to=joannelkoong@gmail.com \
--cc=bernd.schubert@fastmail.fm \
--cc=jefflexu@linux.alibaba.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=shakeel.butt@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox