linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rongwei Wang <rongwei.wang@linux.alibaba.com>
To: "Albert, Des" <des.albert@hpe.com>,
	"mike.kravetz@oracle.com" <mike.kravetz@oracle.com>,
	"songmuchun@bytedance.com" <songmuchun@bytedance.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Additional Huge Pages
Date: Mon, 25 Jul 2022 23:28:06 +0800	[thread overview]
Message-ID: <7c90c2fc-53c2-7495-5833-281575a0fd3c@linux.alibaba.com> (raw)
In-Reply-To: <MW5PR84MB16413DA306CEAAE0DA07BC1698909@MW5PR84MB1641.NAMPRD84.PROD.OUTLOOK.COM>



On 7/23/22 1:20 AM, 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.
Hi Des

It seems an interesting feature.
Is it a transparent huge page? And I can imagine huge page size of 2MB, 
but what's a huge page size of 4 MB, 8 MB, etc.? Two consecutive 2MB 
huge page or four consecutive 2MB huge page? I'm interested in the 
implementation of additional huge pages you described. Because I've 
wanted to try it before, but found that the changes to the kernel were 
quite big.

> 
> 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
> 
> 


      parent reply	other threads:[~2022-07-25 15:28 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
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 [this message]

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=7c90c2fc-53c2-7495-5833-281575a0fd3c@linux.alibaba.com \
    --to=rongwei.wang@linux.alibaba.com \
    --cc=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