lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160407142148.GI5657@arm.com>
Date:	Thu, 7 Apr 2016 15:21:48 +0100
From:	Will Deacon <will.deacon@....com>
To:	Chen Feng <puck.chen@...ilicon.com>
Cc:	catalin.marinas@....com, ard.biesheuvel@...aro.org,
	mark.rutland@....com, akpm@...ux-foundation.org,
	robin.murphy@....com, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, mhocko@...e.com,
	kirill.shutemov@...ux.intel.com, rientjes@...gle.com,
	linux-mm@...ck.org, puck.chen@...mail.com, oliver.fu@...ilicon.com,
	linuxarm@...wei.com, dan.zhao@...ilicon.com,
	suzhuangluan@...ilicon.com, yudongbin@...licon.com,
	albert.lubing@...ilicon.com, xuyiping@...ilicon.com,
	saberlily.xia@...ilicon.com
Subject: Re: [PATCH 1/2] arm64: mem-model: add flatmem model for arm64

On Tue, Apr 05, 2016 at 04:22:51PM +0800, Chen Feng wrote:
> We can reduce the memory allocated at mem-map
> by flatmem.
> 
> currently, the default memory-model in arm64 is
> sparse memory. The mem-map array is not freed in
> this scene. If the physical address is too long,
> it will reserved too much memory for the mem-map
> array.

Can you elaborate a bit more on this, please? We use the vmemmap, so any
spaces between memory banks only burns up virtual space. What exactly is
the problem you're seeing that makes you want to use flatmem (which is
probably unsuitable for the majority of arm64 machines).

Will

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ