Navigation: Linux Kernel Driver DataBase - web LKDDB: Main index - H index
The Linux kernel configuration item CONFIG_HIGHMEM4G
has multiple definitions:
arch/x86/Kconfig
The configuration item CONFIG_HIGHMEM4G:
CONFIG_X86_32
Linux can use up to 4 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 1 Gigabyte 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 "Y" here.
If unsure, say N.
arch/x86/Kconfig
The configuration item CONFIG_HIGHMEM4G:
(none)
Select this if you have a 32-bit processor and between 1 and 4 gigabytes of physical RAM.
arch/i386/Kconfig
The configuration item CONFIG_HIGHMEM4G:
! CONFIG_X86_NUMAQ
Select this if you have a 32-bit processor and between 1 and 4 gigabytes of physical RAM.
Raw data from LKDDb:
(none)
This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).
The data is retrived from:
Popular queries:
Navigation: Linux Kernel Driver DataBase - web LKDDB: main index - H index
Automatically generated (in year 2025). See also LKDDb sources on GitLab