07-07-2009
Quote:
But if I could address 48 bits, that wouldn't be a problem. Right?
You have only 4 GB of RAM installed. You can't get more RAM than what you have installed. If the OS sees 3.5 GB, it correctly sees how much is physically available to it.
A single process will have only 2 GB available to it unless you install some kernel patches which move the shared-memory boundary. On the other hand, if you use shared memory (for postgres, oracle, maybe mysql, large virtual ram disk), you can utilize all of the memory currently in your system.
If you want to expand another gigabyte or so, you'll need PAE or a 64-bit OS.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi!
I'm not a UNIX fanatic but I like using it for the
Oracle database since it's not stable in the Windows NT
environment (what is?).
Problem: Is there any command to show me the amount
of installed physical-memory in the machine? Is
there some other way to show the processes which uses... (4 Replies)
Discussion started by: elgholm
4 Replies
2. UNIX for Dummies Questions & Answers
Is it possible from the command line, or by looking at one of the log files to find out the amount of RAM installed on my SCO Unix 5.05 Server?
I also need to find out H/Disk size and Processor speed but I think i'll do a search of the forums for those ones.
Thanks
RamblasPro (2 Replies)
Discussion started by: RamblasPro
2 Replies
3. UNIX for Advanced & Expert Users
Hi,
how to know size of physical memory under AIX ?
Many thanks.
PS :
man -k memory
man : 0703-310 Fichier man introuvable.
uname -a
AIX server1 1 5 005202DF4C00 (3 Replies)
Discussion started by: big123456
3 Replies
4. Shell Programming and Scripting
I currently have a statistics gathering script i run on my Linux servers. One of the stat i gather is total memory in the machine. The script is all perl with the exception of gathering the memory for that i use the following command:
$ram = (`cat /proc/meminfo | grep "MemTotal" | awk... (1 Reply)
Discussion started by: insania
1 Replies
5. UNIX for Advanced & Expert Users
I was running a program and it stopped and showed "Out of Memory!". at that time, the RAM used by this process is around 4G and the free memory size of the machine is around 30G. Does anybody know what maybe the reason? this program is written with Perl. the OS of the machine is Solaris U8. And I... (1 Reply)
Discussion started by: lilili07
1 Replies
6. Solaris
Is there a command or file I can look at that tells me how much real memory a machine has? A little background. In my shop we run a bunch of java programs, sometimes some of these jobs have config definitions that call for 2G. I would like to know how many I can run before I exhaust rescources. Any... (12 Replies)
Discussion started by: Harleyrci
12 Replies
7. UNIX for Dummies Questions & Answers
i want to avoid writing to a file on the disk. i'd like to do this in memory.
i have a situation where i'm running cat file.txt | head -l 2024 > /tmp/data.txt
now, i check the size of the data.txt by doing a "du -sh /tmp/data.txt
how can i get the size of "head -l 2024" WITHOUT having to... (2 Replies)
Discussion started by: SkySmart
2 Replies
8. Solaris
Hi, looking to upgrade memory on a pair of T5220's from 32GB to 64GB. Cannot determine current DIMM size and slots used. i.e. not sure if Qty 16 x 2GB or Qty 8 x 4GB. If there are no empty slots, i need to go with higher density DIMMs and retire exsisting the 2GB prtdiag follows.
#... (3 Replies)
Discussion started by: edrew
3 Replies
9. Programming
Hello,
Here is a portion of my code:
a=(int *) malloc(dim*dim*sizeof(int));
b=(int *) malloc(dim*dim*sizeof(int));
c=(int *) malloc(dim*dim*sizeof(int));
for(i=0;i<dim;i++)
for(j=0;j<dim;j++)
c= rand();
for(i=0;i<dim;i++)
for(j=0;j<dim;j++)
b=rand();
... (6 Replies)
Discussion started by: chercheur111
6 Replies
10. AIX
Hello facing this problem in VIOS
installed memory shows 32GB
Installed system memory: 32 GB (32768 MB)
Configurable system memory: 16 GB (16384 MB)
Current memory available: 2.23 GB (2288 MB)
Pending memory available: 2.23 GB (2288 MB)
Reserved firmware memory: 560 MB
... (8 Replies)
Discussion started by: filosophizer
8 Replies
LEARN ABOUT SUSE
shm_overview
SHM_OVERVIEW(7) Linux Programmer's Manual SHM_OVERVIEW(7)
NAME
shm_overview - Overview of POSIX shared memory
DESCRIPTION
The POSIX shared memory API allows processes to communicate information by sharing a region of memory.
The interfaces employed in the API are:
shm_open(3) Create and open a new object, or open an existing object. This is analogous to open(2). The call returns a file descriptor
for use by the other interfaces listed below.
ftruncate(2) Set the size of the shared memory object. (A newly created shared memory object has a length of zero.)
mmap(2) Map the shared memory object into the virtual address space of the calling process.
munmap(2) Unmap the shared memory object from the virtual address space of the calling process.
shm_unlink(3) Remove a shared memory object name.
close(2) Close the file descriptor allocated by shm_open(3) when it is no longer needed.
fstat(2) Obtain a stat structure that describes the shared memory object. Among the information returned by this call are the
object's size (st_size), permissions (st_mode), owner (st_uid), and group (st_gid).
fchown(2) To change the ownership of a shared memory object.
fchmod(2) To change the permissions of a shared memory object.
Versions
POSIX shared memory is supported since Linux 2.4 and glibc 2.2.
Persistence
POSIX shared memory objects have kernel persistence: a shared memory object will exist until the system is shut down, or until all pro-
cesses have unmapped the object and it has been deleted with shm_unlink(3)
Linking
Programs using the POSIX shared memory API must be compiled with cc -lrt to link against the real-time library, librt.
Accessing shared memory objects via the file system
On Linux, shared memory objects are created in a (tmpfs) virtual file system, normally mounted under /dev/shm. Since kernel 2.6.19, Linux
supports the use of access control lists (ACLs) to control the permissions of objects in the virtual file system.
CONFORMING TO
POSIX.1-2001.
NOTES
Typically, processes must synchronize their access to a shared memory object, using, for example, POSIX semaphores.
System V shared memory (shmget(2), shmop(2), etc.) is an older semaphore API. POSIX shared memory provides a simpler, and better designed
interface; on the other hand POSIX shared memory is somewhat less widely available (especially on older systems) than System V shared mem-
ory.
SEE ALSO
fchmod(2), fchown(2), fstat(2), ftruncate(2), mmap(2), mprotect(2), munmap(2), shmget(2), shmop(2), shm_open(3), shm_unlink(3), sem_over-
view(7)
COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2008-06-25 SHM_OVERVIEW(7)