From: David Howells <dhowells@redhat.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: dhowells@redhat.com, linux-mm@kvack.org,
Uladzislau Rezki <urezki@gmail.com>,
Dave Chinner <david@fromorbit.com>,
linux-fsdevel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ira Weiny <ira.weiny@intel.com>,
"Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: [PATCH 1/1] mm: Add folio_map_local()
Date: Fri, 28 Oct 2022 17:45:29 +0100 [thread overview]
Message-ID: <64545.1666975529@warthog.procyon.org.uk> (raw)
In-Reply-To: <20221028151526.319681-2-willy@infradead.org>
Matthew Wilcox (Oracle) <willy@infradead.org> wrote:
> Some filesystems benefit from being able to map the entire folio.
> On 32-bit platforms with HIGHMEM, we fall back to using vmap, which
> will be slow. If it proves to be a performance problem, we can look at
> optimising it in a number of ways.
Here's a thought: If a highmem arch has a huge PTEs available, can you create
a huge PTE to cover the folio?
> @@ -426,5 +465,4 @@ static inline void folio_zero_range(struct folio *folio,
> {
> zero_user_segments(&folio->page, start, start + length, 0, 0);
> }
> -
> #endif /* _LINUX_HIGHMEM_H */
Did you want to remove that blank line?
David
next prev parent reply other threads:[~2022-10-28 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 15:15 [PATCH 0/1] Mapping an entire folio Matthew Wilcox (Oracle)
2022-10-28 15:15 ` [PATCH 1/1] mm: Add folio_map_local() Matthew Wilcox (Oracle)
2022-11-01 10:12 ` Hyeonggon Yoo
2022-11-01 10:56 ` Uladzislau Rezki
2022-10-28 16:45 ` David Howells [this message]
2022-10-31 15:11 ` David Howells
2022-10-31 15:14 ` 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=64545.1666975529@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=david@fromorbit.com \
--cc=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--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