08-21-2003
Re: physical memory
Quote:
Originally posted by cchien
It is just a general question....is there a limit on the memory? I am looking into a process to store image files on the unix server which will be accessed by the application, and I just wonder if there is any limit regarding the physical or virtual memory. I am very new to unix, so thanks for any help!
Normally the hardware will limit the maximum amount of RAM a system can use. For example, most 32 bit Intel systems can handle a maximum of 4 gigs of RAM. There are some exceptions, but they are not common.
Swap file size will be limited by the filesystem that they sit on.
10 More Discussions You Might Find Interesting
1. Programming
Hi,
My problem is next....
How can I work with physical memory in the Unix FreeBSD 2.2 or hight?
What is the "mem" & "kmem" drivers?
P.S./ writing device driver for UNIX FreeBSD 2.2 :D (2 Replies)
Discussion started by: Alex_T
2 Replies
2. Shell Programming and Scripting
What command can i use to get the physical and virtual memory of a database? (7 Replies)
Discussion started by: tads98
7 Replies
3. UNIX for Advanced & Expert Users
vmstat -P commands gives me an output as shown at the end of this message.
my first question is about the difference between "total physical memory" and "total physical memory use"
"Total Physical Memory" -"Total Physical Memory Use"
524288 pages-524026 pages= 262 pages
does it mean... (0 Replies)
Discussion started by: gfhgfnhhn
0 Replies
4. Solaris
HI
Please help me how to check the physical memory, model name and hardisk information. (5 Replies)
Discussion started by: jeelans
5 Replies
5. Solaris
what is the command to find the physical memory in soalris OS and how to find whether paging is happening or not ? (2 Replies)
Discussion started by: jayaramanit
2 Replies
6. Solaris
Hi,
Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:-
1. Total Physical Memory in the system(total RAM).
2. Available Physical Memory(i.e. RAM Usage)
3. Total (Logical) Memory in the system
4. Available (Logical) Memory.
I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies
7. Solaris
Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies
8. AIX
IBM says we cannot expand our physical memory on our 570's without upgrading all the existing DIMMS since all slots are currently full. Is it really so difficult for IBM to build servers that leave a couple vacant slots for future expansion? A technical explanation would be greatly appreciated.... (2 Replies)
Discussion started by: 1computerman
2 Replies
9. UNIX for Dummies Questions & Answers
I am currently running unix open server 6.0 on a Dell Power Edge R720. The system will be running fine when the blue screen appears and states the system has performed a physical memory dump in # of ticks. I reboot the system and all looks well. Running diagnostics does not show anything wrong. The... (1 Reply)
Discussion started by: rformt
1 Replies
10. Solaris
Below is Physical Memory result :
-bash-3.00$ prtconf | grep "Memory size"
Memory size: 36854 Megabytes
-bash-3.00$ vmstat 1 2 | tail -1
0 0 0 28220616 1318888 15 143 0 0 0 0 0 253 2 15 0 5215 14989 5917 7 0 93
and the script i have to calculate this in Percentage is :
#!/bin/sh... (3 Replies)
Discussion started by: mjoshi010207
3 Replies
LEARN ABOUT DEBIAN
mlockall
MLOCKALL(2) BSD System Calls Manual MLOCKALL(2)
NAME
mlockall, munlockall -- lock (unlock) the address space of a process
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/mman.h>
int
mlockall(int flags);
int
munlockall(void);
DESCRIPTION
The mlockall() system call locks into memory the physical pages associated with the address space of a process until the address space is
unlocked, the process exits, or execs another program image.
The following flags affect the behavior of mlockall():
MCL_CURRENT Lock all pages currently mapped into the process's address space.
MCL_FUTURE Lock all pages mapped into the process's address space in the future, at the time the mapping is established. Note that this
may cause future mappings to fail if those mappings cause resource limits to be exceeded.
Since physical memory is a potentially scarce resource, processes are limited in how much they can lock down. A single process can lock the
minimum of a system-wide ``wired pages'' limit and the per-process RLIMIT_MEMLOCK resource limit.
The munlockall() call unlocks any locked memory regions in the process address space. Any regions mapped after an munlockall() call will not
be locked.
RETURN VALUES
A return value of 0 indicates that the call succeeded and all pages in the range have either been locked or unlocked. A return value of -1
indicates an error occurred and the locked status of all pages in the range remains unchanged. In this case, the global location errno is
set to indicate the error.
ERRORS
mlockall() will fail if:
[EINVAL] The flags argument is zero, or includes unimplemented flags.
[ENOMEM] Locking the indicated range would exceed either the system or per-process limit for locked memory.
[EAGAIN] Some or all of the memory mapped into the process's address space could not be locked when the call was made.
[EPERM] The calling process does not have the appropriate privilege to perform the requested operation.
SEE ALSO
mincore(2), mlock(2), mmap(2), munmap(2), setrlimit(2)
STANDARDS
The mlockall() and munlockall() functions are believed to conform to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
The mlockall() and munlockall() functions first appeared in FreeBSD 5.1.
BUGS
The per-process resource limit is a limit on the amount of virtual memory locked, while the system-wide limit is for the number of locked
physical pages. Hence a process with two distinct locked mappings of the same physical page counts as 2 pages against the per-process limit
and as only a single page in the system limit.
BSD
June 12, 1999 BSD