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] [day] [month] [year] [list]
Message-ID: <20190923145037.GA1204@dhcp22.suse.cz>
Date:   Mon, 23 Sep 2019 16:50:37 +0200
From:   Michal Hocko <mhocko@...nel.org>
To:     yoav rubin <yoavrubin18@...il.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: linux 32bit kernel virtual space , lowmem , highmem , RAM size

On Wed 11-09-19 19:46:46, yoav rubin wrote:
> Apologize in advance if I'm sending this to the wrong place. (It's my
> first time using mailing list...)
> 
> 
> I need some help understanding the exact relations between the linux
> kernel virtual space , specifically LOWMEM area , and the available
> RAM size as seen by the kernel.

Read through https://www.kernel.org/doc/gorman/

[...]
> For this question I'm ignoring the HIGHMEM area since its not exists
> in my system (turned it off by menuconfig).
[...]
> I know that I'm missing something here because there is no way its true.

If you disable highmem then all the 32b kernel can with is lowmem and
that is defined by the split (1/3 low/high).

-- 
Michal Hocko
SUSE Labs

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ