03-01-2012
Now that you've explained what your system is, a Proliant ProLiant DL360 G5 should actually be able to support 8GB RAM, yes. Most consumer machines from that era would not...
32-bit x86 Linux kernels have different memory models available, configured at compile-time. If you're building your own kernel, inside the 'make menuconfig' menu look for 'high memory support' under 'processor type and features'. select 'off' for most efficient memory use on systems with <=1GB RAM, '4GB' for systems with <=4GB RAM, and 64GB for anything larger.
If you can, look for a precompiled kernel provided by your distribution with 64GB memory support enabled.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
How can i find the total ram in the system?
:confused: (4 Replies)
Discussion started by: orca
4 Replies
2. UNIX for Dummies Questions & Answers
I've just replaced the secondary disk drive (was 4 Gb) with a Seagate Barracuda 7200 200 Gb. However the OS seems to think this is only 500 Mb and a spin speed of 5400, although it correctly recognises the drive as Seagate ST3200822A.
I take it that it still thinks the old drive is attached.... (1 Reply)
Discussion started by: wiggiesworld
1 Replies
3. HP-UX
Hi How Should I know the Total RAM available on HP-UX box? (7 Replies)
Discussion started by: skull123
7 Replies
4. UNIX for Dummies Questions & Answers
Ok, another fun hiccup in my UNIX learning curve. I am trying to count the number of occurrences of an IP address across multiple files named example.hits. I can extract the number of occurrences from the files individually but when you use grep -c with multiple files you get the output similar to... (5 Replies)
Discussion started by: MrAd
5 Replies
5. AIX
Hi,
I've replaced hdisk0 in a Blade server but am having problems re-enabling the mirror as it appears the configuration database is not recognising the new disk.
The first 2 steps to re-enable the mirror fail:
$ extendvg rootvg hdisk0
0516-008 extendvg: LVM system call returned an unknown... (10 Replies)
Discussion started by: m223464
10 Replies
6. Shell Programming and Scripting
Hello,
I want to view server RAM in GB i.e 4 GB or 6 GB via command line to use it in bash script
waiting Any Ideas :)
Thanks :):) (2 Replies)
Discussion started by: LinuxCommandos
2 Replies
7. Red Hat
Hi,
On server 64bit Hw Arch , Linux 5.0(32bit) is installed it is showing only 3gb of ram though physical is 16gb
can u give me idea why? (4 Replies)
Discussion started by: manoj.solaris
4 Replies
8. Shell Programming and Scripting
Good afternoon! Im new at scripting and Im trying to write a script to
calculate total space, total used space and total free space in filesystem names matching a keyword (in this one we will use keyword virginia). Please dont be mean or harsh, like I said Im new and trying my best. Scripting... (4 Replies)
Discussion started by: bigben1220
4 Replies
9. Shell Programming and Scripting
I am aware of the commands to find the total RAM on Linux and Unix for example vmstat.
Can you please tell me which tool / command can give me the Total RAM reading in GBs on Solaris Unix and Linux ? (2 Replies)
Discussion started by: mohtashims
2 Replies
RAM(4) Kernel Interfaces Manual RAM(4)
NAME
ram - ram disk driver
SYNOPSIS
/sys/conf/SYSTEM:
NRAM ram_size # RAM disk size (512-byte blocks)
major device number(s):
block: 3
minor device encoding:
must be zero (0)
DESCRIPTION
The ram pseudo-device provides a very fast extended memory store. It's use is intended for file systems like /tmp and applications which
need to access a reasonably large amount of data quickly.
The amount of memory dedicated to the ram device is controlled by the NRAM definition in units of 512-byte blocks. This is also patchable
in the system binary through the variable ram_size (though a patched system would have to be rebooted before any change took effect; see
adb(1)). This makes it easy to test the effects of different ram disk sizes on system performance. It's important to note that any space
given to the ram device is permanently allocated at system boot time. Dedicating too much memory can adversely affect system performance
by forcing the system to swap heavily as in a memory poor environment.
The block file accesses the ram disk via the system's buffering mechanism through a buffer sharing arrangement with the buffer cache. It
may be read and written without regard to physical disk records. There is no `raw' interface since no speed advantage is gained by such an
interface with the ram disk.
DISK SUPPORT
The ram driver does not support pseudo-disks (partitions). The special files refer to the entire `drive' as a single sequentially
addressed file.
A typical use for the ram disk would be to mount /tmp on it. Note that if this arrangement is recorded in /etc/fstab then /etc/rc will
have to be modified slightly to do a mkfs(8) on the ram disk before the standard file system checks are done.
FILES
/dev/ram block file
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
hk(4), ra(4), rl(4), rk(4), rp(4), rx(4), si(4), xp(4) dtab(5), autoconfig(8)
DIAGNOSTICS
ram: no space. There is not enough memory to allocate the space needed by the ram disk. The ram disk is disabled. Any attempts to access
it will return an error.
ram: not allocated. No memory was allocated to the ram disk and an attempt was made to open it. Either not enough memory was available at
boot time or the kernel variable ram_size was set to zero.
BUGS
The ram driver is only available under 2.11BSD.
3rd Berkeley Distribution Januray 27, 1996 RAM(4)