linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Albert, Des" <des.albert@hpe.com>
To: "mike.kravetz@oracle.com" <mike.kravetz@oracle.com>,
	"songmuchun@bytedance.com" <songmuchun@bytedance.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Additional Huge Pages
Date: Fri, 22 Jul 2022 17:20:54 +0000	[thread overview]
Message-ID: <MW5PR84MB16413DA306CEAAE0DA07BC1698909@MW5PR84MB1641.NAMPRD84.PROD.OUTLOOK.COM> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 956 bytes --]

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.

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.

Thanks
Des

Dr Des Albert
HPC Software Product Manager
+1 360 312 6169
des.albert@hpe.com<mailto:des.albert@hpe.com>

[cid:image001.gif@01D89DAF.A3F91F80]  Hewlett Packard Enterprise


[-- Attachment #1.2: Type: text/html, Size: 6302 bytes --]

[-- Attachment #2: image001.gif --]
[-- Type: image/gif, Size: 240 bytes --]

             reply	other threads:[~2022-07-22 17:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 17:20 Albert, Des [this message]
2022-07-22 18:12 ` Mike Kravetz
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=MW5PR84MB16413DA306CEAAE0DA07BC1698909@MW5PR84MB1641.NAMPRD84.PROD.OUTLOOK.COM \
    --to=des.albert@hpe.com \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --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