From: Mike Kravetz <mike.kravetz@oracle.com>
To: "Albert, Des" <des.albert@hpe.com>
Cc: "songmuchun@bytedance.com" <songmuchun@bytedance.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Additional Huge Pages
Date: Fri, 22 Jul 2022 11:12:15 -0700 [thread overview]
Message-ID: <Ytrof5bCuL2CNlCu@monkey> (raw)
In-Reply-To: <MW5PR84MB16413DA306CEAAE0DA07BC1698909@MW5PR84MB1641.NAMPRD84.PROD.OUTLOOK.COM>
On 07/22/22 17:20, Albert, Des wrote:
> Hi
>
> I am the Product Manager for the HPE Cray Operating System ( formerly Cray Linux Environment )
>
> One of the features of this product is a component known as additional huge pages. This is kernel code that enables the selection of 'non-standard' huge page sizes.
> For example, the current implementation allows for selection of huge page sizes of 2, 4, 8, 16, 32, 64, 128, 256 and 512 MB as well as 1 and 2 GB.
>
Interesting.
Are these non-standard huge pages sizes targeted at application usage,
or internal kernel APIs. If applications, what API is used? Is it
similar/the same as hugetlb?
Within the kernel, support for 'arbitrary page sizes' is provided by the
folio abstraction. hugetlb code will be moving to that in the future.
Any new code such as this whould be based on folios.
> We are currently evaluating the concept of providing this code to kernel.org. I realize that this would require dedication of technical resources to work with maintainers.
>
> I would like to know if there is interest in this suggestion. I realize that Transparent Huge Pages may be regarded as a more general approach to this requirement.
>
I guess interest would depend on the use cases and potential advantages
of this feature. You should be able to speak to this based on your
current usage.
--
Mike Kravetz
next prev parent reply other threads:[~2022-07-22 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 17:20 Albert, Des
2022-07-22 18:12 ` Mike Kravetz [this message]
2022-07-22 19:20 ` Albert, Des
2022-07-22 19:39 ` Matthew Wilcox
2022-07-22 19:53 ` Albert, Des
2022-07-27 22:48 ` Albert, Des
2022-12-21 23:43 ` Albert, Des
2022-07-25 15:28 ` Rongwei Wang
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=Ytrof5bCuL2CNlCu@monkey \
--to=mike.kravetz@oracle.com \
--cc=des.albert@hpe.com \
--cc=linux-mm@kvack.org \
--cc=songmuchun@bytedance.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