From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] fuse: Convert fuse_writepage_locked to take a folio
Date: Sat, 13 Apr 2024 13:28:31 +0200 [thread overview]
Message-ID: <13cbb507-45b5-48fb-a696-cb43ad14a5b2@fastmail.fm> (raw)
In-Reply-To: <20240228182940.1404651-2-willy@infradead.org>
On 2/28/24 19:29, Matthew Wilcox (Oracle) wrote:
> The one remaining caller of fuse_writepage_locked() already has a folio,
> so convert this function entirely. Saves a few calls to compound_head()
> but no attempt is made to support large folios in this patch.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> ---
> fs/fuse/file.c | 30 +++++++++++++++---------------
> 1 file changed, 15 insertions(+), 15 deletions(-)
>
> diff --git a/fs/fuse/file.c b/fs/fuse/file.c
> index 340ccaafb3f7..f173cbce1d31 100644
> --- a/fs/fuse/file.c
> +++ b/fs/fuse/file.c
> @@ -2040,26 +2040,26 @@ static void fuse_writepage_add_to_bucket(struct fuse_conn *fc,
> rcu_read_unlock();
> }
>
> -static int fuse_writepage_locked(struct page *page)
> +static int fuse_writepage_locked(struct folio *folio)
> {
> - struct address_space *mapping = page->mapping;
> + struct address_space *mapping = folio->mapping;
> struct inode *inode = mapping->host;
> struct fuse_conn *fc = get_fuse_conn(inode);
> struct fuse_inode *fi = get_fuse_inode(inode);
> struct fuse_writepage_args *wpa;
> struct fuse_args_pages *ap;
> - struct page *tmp_page;
> + struct folio *tmp_folio;
> int error = -ENOMEM;
>
> - set_page_writeback(page);
> + folio_start_writeback(folio);
>
> wpa = fuse_writepage_args_alloc();
> if (!wpa)
> goto err;
> ap = &wpa->ia.ap;
>
> - tmp_page = alloc_page(GFP_NOFS | __GFP_HIGHMEM);
> - if (!tmp_page)
> + tmp_folio = folio_alloc(GFP_NOFS | __GFP_HIGHMEM, 0);
> + if (!tmp_folio)
> goto err_free;
>
> error = -EIO;
> @@ -2068,21 +2068,21 @@ static int fuse_writepage_locked(struct page *page)
> goto err_nofile;
>
> fuse_writepage_add_to_bucket(fc, wpa);
> - fuse_write_args_fill(&wpa->ia, wpa->ia.ff, page_offset(page), 0);
> + fuse_write_args_fill(&wpa->ia, wpa->ia.ff, folio_pos(folio), 0);
>
> - copy_highpage(tmp_page, page);
> + folio_copy(tmp_folio, folio);
> wpa->ia.write.in.write_flags |= FUSE_WRITE_CACHE;
> wpa->next = NULL;
> ap->args.in_pages = true;
> ap->num_pages = 1;
> - ap->pages[0] = tmp_page;
> + ap->pages[0] = &tmp_folio->page;
Hi Matthew,
sorry for late review. The part I'm totally confused with (already
without this patch), why is this handling a single page only and not the
entire folio? Is it guaranteed that the folio has a single page only?
Thanks,
Bernd
next prev parent reply other threads:[~2024-04-13 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 18:29 [PATCH 1/2] fuse: Remove fuse_writepage Matthew Wilcox (Oracle)
2024-02-28 18:29 ` [PATCH 2/2] fuse: Convert fuse_writepage_locked to take a folio Matthew Wilcox (Oracle)
2024-04-13 11:28 ` Bernd Schubert [this message]
2024-04-13 15:59 ` Matthew Wilcox
2024-04-15 12:48 ` Bernd Schubert
2024-03-05 14:15 ` [PATCH 1/2] fuse: Remove fuse_writepage Miklos Szeredi
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=13cbb507-45b5-48fb-a696-cb43ad14a5b2@fastmail.fm \
--to=bernd.schubert@fastmail.fm \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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;
as well as URLs for NNTP newsgroup(s).