From: Matthew Wilcox <willy@infradead.org>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: linux-mm@kvack.org, linux-s390@vger.kernel.org
Subject: Inaccessible pages & folios
Date: Fri, 9 Apr 2021 20:40:59 +0100 [thread overview]
Message-ID: <20210409194059.GW2531743@casper.infradead.org> (raw)
Hi Claudio,
I'm working on making the page cache manage memory in larger chunks than
PAGE_SIZE [1] [2]. In doing so, I came across this call that you added:
@@ -2807,6 +2807,13 @@ int __test_set_page_writeback(struct page *page, bool keep_write)
inc_zone_page_state(page, NR_ZONE_WRITE_PENDING);
}
unlock_page_memcg(page);
+ access_ret = arch_make_page_accessible(page);
I'm going to change __test_set_page_writeback() to take a folio [3] and
now I'm wondering what interface you'd like to use. My preference would
be to rename arch_make_page_accessible() to arch_make_folio_accessible()
and pass a folio, at which time you would make the entire folio (however
many pages might be in it) accessible. If you would rather, we can
leave the interface as arch_make_page_accessible(), in which case we'll
just call it N times in __test_set_page_writeback() (and I won't need
to touch gup.c).
Let me know what you want.
[1] https://lwn.net/Articles/849538/
[2] https://lore.kernel.org/linux-mm/20210409185105.188284-1-willy@infradead.org/
[3] https://git.infradead.org/users/willy/pagecache.git/commitdiff/85297eb08f1b034b9652ea63dd053e3be4d7de7f
PS: The prototype is in gfp.h. That's not really appropriate; gfp.h
is about allocating memory, and this call really has nothing to do with
memory allocation. I think mm.h is a better place for it, if you can't
find a better header file than that.
next reply other threads:[~2021-04-09 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 19:40 Matthew Wilcox [this message]
2021-04-12 12:18 ` Claudio Imbrenda
2021-04-12 12:43 ` Matthew Wilcox
2021-04-12 13:37 ` Claudio Imbrenda
2021-04-12 13:55 ` Matthew Wilcox
2021-04-15 9:28 ` Claudio Imbrenda
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=20210409194059.GW2531743@casper.infradead.org \
--to=willy@infradead.org \
--cc=imbrenda@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.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