From: nkela@cisco.com (Nikunj Kela (nkela))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: add support for 43bit physical address
Date: Tue, 3 Jul 2018 18:35:32 +0000 [thread overview]
Message-ID: <1530642932209.57184@cisco.com> (raw)
In-Reply-To: <20180703145626.g6pb4bgnrle2p2qf@armageddon.cambridge.arm.com>
We are trying to reduce the memory allocation needed for kdump kernel. We want to reserve less than 32M for kdump kernel if possible. We are able to get ~14M saving by the proposed change. Below are the numbers before and after the proposed change:
With 48 bit physical address and 30 bit section size:
--------------------------------------------------------------------
Memory: 23052K/49152K available (3460K kernel code, 296K rwdata, 2436K rodata, 204K init, 179K bss, 26100K reserved, 0K cma-reserved)
With 43 bit physical address and 27bit section size:
--------------------------------------------------------------------
Memory: 37284K/49152K available (3596K kernel code, 296K rwdata, 2408K rodata, 208K init, 173K bss, 11868K reserved, 0K cma-reserved)
Thanks,
-Nikunj
________________________________________
From: Catalin Marinas <catalin.marinas@arm.com>
Sent: Tuesday, July 3, 2018 7:56 AM
To: Nikunj Kela (nkela)
Cc: Will Deacon; xe-kernel at external.cisco.com; linux-kernel at vger.kernel.org; linux-arm-kernel at lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: add support for 43bit physical address
On Mon, Jul 02, 2018 at 02:04:51PM -0700, Nikunj Kela wrote:
> This patch adds support for 43bit physical address. Additionally,
> this patch adds support for 27bit section size. This is useful in
> reducing kernel memory usage. One usecase is in kdump kernel.
Some numbers please.
--
Catalin
next prev parent reply other threads:[~2018-07-03 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 21:04 [PATCH 2/2] arm64: add support for 43bit physical address Nikunj Kela
2018-07-03 14:56 ` Catalin Marinas
2018-07-03 18:35 ` Nikunj Kela (nkela) [this message]
2018-07-05 18:34 ` Catalin Marinas
2018-07-05 23:40 ` Nikunj Kela (nkela)
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=1530642932209.57184@cisco.com \
--to=nkela@cisco.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).