From: Rik van Riel <riel@surriel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com, Matthew Wilcox <willy@infradead.org>,
Yang Shi <shy828301@gmail.com>
Subject: [PATCH v2] mm: align larger anonymous mappings on THP boundaries
Date: Tue, 9 Aug 2022 14:24:57 -0400 [thread overview]
Message-ID: <20220809142457.4751229f@imladris.surriel.com> (raw)
Align larger anonymous memory mappings on THP boundaries by
going through thp_get_unmapped_area if THPs are enabled for
the current process.
With this patch, larger anonymous mappings are now THP aligned.
When a malloc library allocates a 2MB or larger arena, that
arena can now be mapped with THPs right from the start, which
can result in better TLB hit rates and execution time.
Signed-off-by: Rik van Riel <riel@surriel.com>
---
v2: avoid the chicken & egg issue with MMF_VM_HUGEPAGE (Yang Shi)
mm/mmap.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mm/mmap.c b/mm/mmap.c
index c035020d0c89..1d859893436d 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -2229,6 +2229,9 @@ get_unmapped_area(struct file *file, unsigned long addr, unsigned long len,
*/
pgoff = 0;
get_area = shmem_get_unmapped_area;
+ } else if (IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE)) {
+ /* Ensures that larger anonymous mappings are THP aligned. */
+ get_area = thp_get_unmapped_area;
}
addr = get_area(file, addr, len, pgoff, flags);
--
2.37.1
next reply other threads:[~2022-08-09 18:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 18:24 Rik van Riel [this message]
2022-08-10 17:06 ` [PATCH v2] mm: align larger anonymous mappings on THP boundaries Yang Shi
2024-01-16 11:53 ` Jiri Slaby
2024-01-16 12:09 ` Jiri Slaby
2024-01-16 19:16 ` Suren Baghdasaryan
2024-01-16 20:56 ` Yang Shi
2024-01-16 21:57 ` Suren Baghdasaryan
2024-01-16 22:25 ` Yang Shi
2024-01-16 22:30 ` Suren Baghdasaryan
2024-01-16 23:14 ` Yang Shi
2024-01-17 17:40 ` Kees Cook
2024-01-17 23:32 ` Yang Shi
2024-01-18 0:01 ` Suren Baghdasaryan
2024-01-18 0:13 ` Yang Shi
2024-01-18 0:29 ` Suren Baghdasaryan
2024-01-18 1:34 ` Suren Baghdasaryan
2024-01-18 2:10 ` Suren Baghdasaryan
2024-01-16 20:55 ` Yang Shi
2024-01-18 0:07 ` Yang Shi
2024-01-18 0:09 ` Suren Baghdasaryan
2024-01-18 0:11 ` Suren Baghdasaryan
2024-01-18 0:15 ` Yang Shi
2024-01-18 0:28 ` Suren Baghdasaryan
2024-01-18 7:04 ` Jiri Slaby
2024-01-18 17:48 ` Suren Baghdasaryan
2024-01-18 18:42 ` Yang Shi
2024-01-18 18:42 ` Yang Shi
2024-01-20 13:43 ` Linux regression tracking #adding (Thorsten Leemhuis)
2024-01-20 15:47 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=20220809142457.4751229f@imladris.surriel.com \
--to=riel@surriel.com \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@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;
as well as URLs for NNTP newsgroup(s).