From: Yang Shi <shy828301@gmail.com>
To: Rik van Riel <riel@surriel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, kernel-team@fb.com,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] mm: align larger anonymous mappings on THP boundaries
Date: Tue, 9 Aug 2022 10:16:46 -0700 [thread overview]
Message-ID: <CAHbLzkrdsHd1UhUAVr1MH3HzauyUT5Cy0VyRzeu123ohhKS8-g@mail.gmail.com> (raw)
In-Reply-To: <20220808164658.5079a9a0@imladris.surriel.com>
On Mon, Aug 8, 2022 at 1:47 PM Rik van Riel <riel@surriel.com> wrote:
>
> 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 checking in /proc/PID/maps, but only when THP is enabled
> for that process.
>
> Signed-off-by: Rik van Riel <riel@surriel.com>
> ---
> mm/mmap.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/mm/mmap.c b/mm/mmap.c
> index c035020d0c89..3a9d19cec690 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 (test_bit(MMF_VM_HUGEPAGE, ¤t->mm->flags)) {
There is a kind of chicken & egg problem here, MMF_VM_HUGEPAGE is not
going to be set if there is no THP eligible vma even though THP is
enabled.
> + /* 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 prev parent reply other threads:[~2022-08-09 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 20:46 Rik van Riel
2022-08-08 22:09 ` Andrew Morton
2022-08-09 0:59 ` Rik van Riel
2022-08-09 17:16 ` Yang Shi [this message]
2022-08-09 17:36 ` Rik van Riel
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=CAHbLzkrdsHd1UhUAVr1MH3HzauyUT5Cy0VyRzeu123ohhKS8-g@mail.gmail.com \
--to=shy828301@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@fb.com \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.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