public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: chenfeng <puck.chen@hisilicon.com>
To: <catalin.marinas@arm.com>, <will.deacon@arm.com>,
	<mark.rutland@arm.com>, <ard.biesheuvel@linaro.org>,
	<lauraa@codeaurora.org>, <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Cc: Yiping Xu <xuyiping@hisilicon.com>, <oliver.fu@hisilicon.com>,
	<suzhuangluan@hisilicon.com>, Dan zhao <dan.zhao@hisilicon.com>,
	"Peter Panshilin" <peter.panshilin@hisilicon.com>,
	qijiwen <qijiwen@hisilicon.com>
Subject: Question about the sparse memory section size
Date: Tue, 22 Sep 2015 16:14:21 +0800	[thread overview]
Message-ID: <56010DDD.3080803@hisilicon.com> (raw)

Hi all,
The sparse memory section size, SECTION_SIZE_BITS, currently is 1GB for arm64 by default. However, it might generate wasted memmap memory space for those memory sections less than 1GB. e.g.
for 512MB memory section, still 14MB(sizeof(struct page) * PAGES_PER_SECTION) memmap needs to be reserved. The wasted memmap space could be eliminated by changing memory section size from 1GB to 512M, but still some questions to be answered,

1) why arm64 uses 1GB as default setting?
2) any risk to change section size from 1GB to 512MB? like, any impact to performance since memory section number is increased.


Any help will be appreciated.

Puck


             reply	other threads:[~2015-09-22  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22  8:14 chenfeng [this message]
2015-09-22 11:17 ` Question about the sparse memory section size Dave Martin
     [not found]   ` <13BC74040D0EF941B37FE727464B56DA8A5E2696@szxema508-mbx.china.huawei.com>
2015-09-23 12:08     ` 答复: " Dave P Martin

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=56010DDD.3080803@hisilicon.com \
    --to=puck.chen@hisilicon.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=dan.zhao@hisilicon.com \
    --cc=lauraa@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=oliver.fu@hisilicon.com \
    --cc=peter.panshilin@hisilicon.com \
    --cc=qijiwen@hisilicon.com \
    --cc=suzhuangluan@hisilicon.com \
    --cc=will.deacon@arm.com \
    --cc=xuyiping@hisilicon.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