← Back to team overview

sslug-teknik team mailing list archive

Re: Mx RAM size på IA64?

 

In <3DC134CD.7070305@xxxxxxxx> Kristian Vilmann <kvi@xxxxxxxx> writes:

>Jeg fik lige dagens præmiespørgsmål:

>Hvor meget ram kan Linux på IA64 håndtere?

Meget ... det afhænger lidt af om vi snakker Linux 2.4 eller 2.5.
For 2.4 kernen er svaret 64 GB, ved brug af "highmem" optionen.
Fra Documentation/Configure.help:

CONFIG_NOHIGHMEM
  Linux can use up to 64 Gigabytes of physical memory on x86 systems.
  However, the address space of 32-bit x86 processors is only 4
  Gigabytes large. That means that, if you have a large amount of
  physical memory, not all of it can be "permanently mapped" by the
  kernel. The physical memory that's not permanently mapped is called
  "high memory".

  If you are compiling a kernel which will never run on a machine with
  more than 960 megabytes of total physical RAM, answer "off" here
  (default
  choice and suitable for most users). This will result in a "3GB/1GB"
  split: 3GB are mapped so that each process sees a 3GB virtual memory
  space and the remaining part of the 4GB virtual memory space is used
  by the kernel to permanently map as much physical memory as
  possible.

  If the machine has between 1 and 4 Gigabytes physical RAM, then
  answer "4GB" here.

  If more than 4 Gigabytes is used then answer "64GB" here. This
  selection turns Intel PAE (Physical Address Extension) mode on.
  PAE implements 3-level paging on IA32 processors. PAE is fully
  supported by Linux, PAE mode is implemented on all recent Intel
  processors (Pentium Pro and better). NOTE: If you say "64GB" here,
  then the kernel will not boot on CPUs that don't support PAE!


Hvis man kigger på 2.5 kernerne, så mener jeg at der er support for
det fulde adresserum v.h.a. "hugetlb" og lignende forbedringer i
kernen.

-- 
Henrik Storner <henrik@xxxxxxx> 
Hvis du vil have god, pålidelig info om Open Source og Linux, så 
overvej at støtte Linux Weekly News med et abonnement.
                                   http://lwn.net/Articles/10688/


Follow ups

References