≡ Menu

system memory

This is an user contributed article.

When it is time to upgrade the memory on a Linux host, it is important to understand the existing memory information of the system, which will help to plan the memory upgrade appropriately without opening server chassis (especially, when you have Linux rack mount server).

What is the current total RAM used in the system?

This can be obtained using free command or from the /proc/meminfo file as shown below. In this example, the current RAM is 1GB.
# free
Sample output:

             total       used       free     shared    buffers     cached
Mem:       2074016    2002592      71424          0     480908     937296
-/+ buffers/cache:     584388    1489628
Swap:      1951888      79116    1872772

You can also display memory ram, info using /proc file, enteR:
# grep MemTotal /proc/meminfo
Sample output:

MemTotal:      1034624 kB

What is the maximum RAM supported by the system?

You can use dmidecode command to query all memory related information from the system DMI table. In this example, the maximum RAM supported by the system is 8 GB as shown below.

# dmidecode -t 16
Sample output:

# dmidecode 2.9
SMBIOS 2.3 present.
Handle 0x1000, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: Multi-bit ECC
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 4

How many memory slots are available for expansion?

# dmidecode -t 17 | grep Size
Sample output:

        Size: 512 MB
        Size: 512 MB
        Size: No Module Installed
        Size: No Module Installed


dmidecode can also be used to identify details about several other hardware related information. dmidecode command reads the systems DMI table for the hardware and BIOS information. DMI stands for Desktop Management interface and SMBIOS stands for System Management BIOS.

Distributed Management Task Force maintains the DMI and SMBIOS specification:

This small guide may come handy...

From the article:

One great thing about Linux is that you can transplant a hard disk from a machine that runs a 32-bit AMD XP processor into a new 64-bit Intel Core 2 machine, and the Linux installation will continue to work. However, if you do this, you'll be running a 32-bit kernel, a C library, and a complete system install on a processor that could happily run 64-bit code. You'll waste even more resources if your new machine has 4GB or more of system memory, and you'll be forced to either not use some of it or run a 32-bit Physical Address Extension (PAE) kernel. Cross-grading to the 64-bit variant of your Linux distribution can help you use your resources more wisely. A disclaimer: changing the architecture of your Fedora installation from 32 to 64-bit isn't recommended or supported in any way. Perform this at your own risk after creating a suitable backup.

=> Upgrade from 32-bit to 64-bit Fedora Linux without a system reinstall [linux.com]