linux-kernel - Re: Linux kernel memory and split on 64-bit machines

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>] [day] [month] [year] [list]

Date:	Mon, 29 Oct 2007 16:48:01 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Yoav Artzi <yoavar@...ckpoint.com>
Cc:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: Linux kernel memory and split on 64-bit machines

On Mon, Oct 29, 2007 at 05:06:31PM +0200, Yoav Artzi wrote:
> I don't know what befell me. I realized the foolishness of the questions 
> a second after clicking the send button.
> 
> 
> Now, I just wonder what will happen when people will need more then 
> 2^46bytes of memory. Any idea?

The CPU needs to be extended then beyond 48bit VA.

(actually it could be extended to 2^46.5 or so) 


> 
> Another two issues:
> 
> 1. I see vmalloc() doesn't cover the entire possible space. Why is that?

It needs an reserved space for its virtual mappings.

> 
> 2. How come user space gets 47bits and kernel only gets 46bits in direct 
> mapping?

Half of the kernel space is reserved for special purposes 
(vmalloc, ioremap etc.) That is not fixed and could be varied.

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/