mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nitin.m.gupta@oracle.com
Cc: mike.kravetz@oracle.com, akpm@linux-foundation.org,
	julian.calaby@gmail.com, hughd@google.com,
	adam.buchbinder@gmail.com, kirill.shutemov@linux.intel.com,
	sfr@canb.auug.org.au, paul.gortmaker@windriver.com,
	thomas.tai@oracle.com, chris.hyser@oracle.com,
	khalid.aziz@oracle.com, atish.patra@oracle.com, mhocko@suse.com,
	sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] sparc64: Multi-page size support
Date: Thu, 23 Feb 2017 11:32:18 -0500 (EST)	[thread overview]
Message-ID: <20170223.113218.2219144071313988229.davem@davemloft.net> (raw)
In-Reply-To: <1485994656-115830-1-git-send-email-nitin.m.gupta@oracle.com>

From: Nitin Gupta <nitin.m.gupta@oracle.com>
Date: Wed,  1 Feb 2017 16:16:36 -0800

> Add support for using multiple hugepage sizes simultaneously
> on mainline. Currently, support for 256M has been added which
> can be used along with 8M pages.
> 
> Page tables are set like this (e.g. for 256M page):
>     VA + (8M * x) -> PA + (8M * x) (sz bit = 256M) where x in [0, 31]
> 
> and TSB is set similarly:
>     VA + (4M * x) -> PA + (4M * x) (sz bit = 256M) where x in [0, 63]
> 
> - Testing
> 
> Tested on Sonoma (which supports 256M pages) by running stream
> benchmark instances in parallel: one instance uses 8M pages and
> another uses 256M pages, consuming 48G each.
> 
> Boot params used:
> 
> default_hugepagesz=256M hugepagesz=256M hugepages=300 hugepagesz=8M
> hugepages=10000
> 
> Signed-off-by: Nitin Gupta <nitin.m.gupta@oracle.com>

Applied, thanks.

      reply	other threads:[~2017-02-23 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02  0:16 Nitin Gupta
2017-02-23 16:32 ` David Miller [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=20170223.113218.2219144071313988229.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=adam.buchbinder@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=atish.patra@oracle.com \
    --cc=chris.hyser@oracle.com \
    --cc=hughd@google.com \
    --cc=julian.calaby@gmail.com \
    --cc=khalid.aziz@oracle.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.com \
    --cc=mike.kravetz@oracle.com \
    --cc=nitin.m.gupta@oracle.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sparclinux@vger.kernel.org \
    --cc=thomas.tai@oracle.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

all inboxes | Powered by JetHome®