From: Matthew Wilcox <willy@infradead.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: "Theodore Y . Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fscrypt: Change fscrypt_encrypt_pagecache_blocks() to take a folio
Date: Fri, 21 Feb 2025 05:35:09 +0000 [thread overview]
Message-ID: <Z7gQjS34D_Xg_uVo@casper.infradead.org> (raw)
In-Reply-To: <20250221051607.GA1259@sol.localdomain>
On Thu, Feb 20, 2025 at 09:16:07PM -0800, Eric Biggers wrote:
> On Fri, Feb 21, 2025 at 05:10:01AM +0000, Matthew Wilcox (Oracle) wrote:
> > ext4 and ceph already have a folio to pass; f2fs needs to be properly
> > converted but this will do for now. This removes a reference
> > to page->index and page->mapping as well as removing a call to
> > compound_head().
> >
> > Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
>
> It's still assumed to be a small folio though, right? It still just allocates a
> "bounce page", not a "bounce folio".
Yup, I haven't figured out how to do large folio support, so any
filesystem using fscrypt can't support large folios for now. I'm
working on "separate folio and page" at the moment rather than "enable
large folios everywhere". Maybe someone else will figure out how to
support large folios in fscrypt and I won't have to ;-)
next prev parent reply other threads:[~2025-02-21 5:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 5:10 [PATCH] fscrypt: Change fscrypt_encrypt_pagecache_blocks() to take a folio Matthew Wilcox (Oracle)
2025-02-21 5:16 ` Eric Biggers
2025-02-21 5:35 ` Matthew Wilcox [this message]
2025-02-21 21:09 ` Eric Biggers
2025-02-21 22:22 ` Matthew Wilcox
2025-02-21 22:41 ` Eric Biggers
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=Z7gQjS34D_Xg_uVo@casper.infradead.org \
--to=willy@infradead.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.