From: Muchun Song <muchun.song@linux.dev>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Linux-MM <linux-mm@kvack.org>, Yuan Can <yuancan@huawei.com>
Subject: Re: [PATCH resend] mm: hugetlb_vmemmap: use bulk allocator in alloc_vmemmap_page_list()
Date: Wed, 6 Sep 2023 10:41:35 +0800 [thread overview]
Message-ID: <F0A2FAEE-F453-484E-80D0-C78A42DFBD02@linux.dev> (raw)
In-Reply-To: <20230905103508.2996474-1-wangkefeng.wang@huawei.com>
> On Sep 5, 2023, at 18:35, Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
>
> It is needed 4095 pages(1G) or 7 pages(2M) to be allocated once in
> alloc_vmemmap_page_list(), so let's add a bulk allocator varietas
> alloc_pages_bulk_list_node() and switch alloc_vmemmap_page_list()
> to use it to accelerate page allocation.
>
> Simple test on arm64's qemu with 1G Hugetlb, 870,842ns vs 3,845,252ns,
> even if there is a certain fluctuation, it is still a nice improvement.
>
> Tested-by: Yuan Can <yuancan@huawei.com>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
Reviewed-by: Muchun Song <songmuchun@bytedance.com>
Thanks.
next prev parent reply other threads:[~2023-09-06 2:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 10:35 Kefeng Wang
2023-09-06 2:41 ` Muchun Song [this message]
2023-09-06 2:47 ` Matthew Wilcox
2023-09-06 3:13 ` Kefeng Wang
2023-09-06 3:14 ` Matthew Wilcox
2023-09-06 12:32 ` Kefeng Wang
2023-09-06 3:25 ` Muchun Song
2023-09-06 9:33 ` Kefeng Wang
2023-09-06 14:32 ` Muchun Song
2023-09-06 14:58 ` Kefeng Wang
2023-09-07 6:35 ` Muchun Song
2023-10-25 9:32 ` Mel Gorman
2023-10-25 13:50 ` kernel test robot
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=F0A2FAEE-F453-484E-80D0-C78A42DFBD02@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yuancan@huawei.com \
/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