linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Linux Memory Management List <linux-mm@kvack.org>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Mixed page compact code and (higher order) folios for filemap
Date: Thu, 16 Nov 2023 14:11:00 +1030	[thread overview]
Message-ID: <ec608bc8-e07b-49e6-a01e-487e691220f5@gmx.com> (raw)

Hi guys,

I'm wondering if there is any pitfalls when mixing the legacy page based
code with higher order (order >= 1) folios.

E.g. if I allocated a folio with order 2, attached some private data to
the folio, then call filemap_add_folio().

Later some one called find_lock_page() and hit the 2nd page of that folio.

I believe the regular IO is totally fine, but what would happen for the
page->private of that folio?
Would them all share the same value of the folio_attach_private()? Or
some different values?

Thanks,
Qu

             reply	other threads:[~2023-11-16  3:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16  3:41 Qu Wenruo [this message]
2023-11-16  5:05 ` Mixed page compact code and (higher order) folios for filemap Matthew Wilcox
2023-11-16  5:30   ` Qu Wenruo
2023-11-16 14:23     ` Matthew Wilcox
2023-11-16 20:33       ` Qu Wenruo
2023-11-16 22:40       ` Qu Wenruo
2023-11-17 13:36         ` Matthew Wilcox

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=ec608bc8-e07b-49e6-a01e-487e691220f5@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.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).