08-12-2008
I merged the two threads, thanks for alerting me, Zaxxon.
big123456, "post this in the AIX forum" is not an invitation to crosspost or double post, but just the suggestion to put a question where it thematically belongs. In fact posting the same in more than one forum is forbidden by the
rules. You are here since 2005 and should know that by now.
Thanks for your consideration.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
can anyone explain me what virtual memory is ( for which we use vmstat commande line ) comparing with RAM ?
many thanks before. (2 Replies)
Discussion started by: big123456
2 Replies
2. Programming
Hi,
First of all I appreciate this group very much for its informative discussions and posts.
Here is my question.
I have one process whose virtual memory size increases linearly from 6MB to 12MB in 20 minutes. Does that mean my process has memory leaks?
In what cases does the... (4 Replies)
Discussion started by: shriashishpatil
4 Replies
3. HP-UX
Hi!
I work with HP-UX and I have to monitorize the use of virtual memory for different processes.
(java processes for Tibco Adapter) And if these processes exceed a limit send a message to the syslog.
I donīt know how to monitorize this...
Should I do a script? or use an aplication, for example... (3 Replies)
Discussion started by: Kurohana
3 Replies
4. UNIX for Dummies Questions & Answers
Hi All,
Does anyone know what the best commands in the UNIX command line are for obtaining this info:
current CPU usage
memory usage
virtual memory usage
preferably with date and time parameters too?
thanks
ocelot (4 Replies)
Discussion started by: ocelot
4 Replies
5. UNIX for Dummies Questions & Answers
Hi,
Can anyone please help me workout how much virtual memory I have running on a T2000 running Solaris 10. Thanks
# df -h
swap 3.5G 1.0M 3.5G 1% /etc/svc/volatile
swap 3.5G 208K 3.5G 1% /tmp
swap 3.5G 56K ... (2 Replies)
Discussion started by: jamba1
2 Replies
6. 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
7. Solaris
Hello solaris experts,
Being new to solaris containers, from Linux, feeling difficulty in understanding certain concepts. Hope somebody can help me here.
I understand that, & some questions ....
Locked memory -- memory which will not be swapped out at any cause.
is this for... (0 Replies)
Discussion started by: thegeek
0 Replies
8. Solaris
One of our project has exceeded its assigned max-memory-locked by 3 times .. The said project is using around 9 gigs as described by rss parameter in prstat -J .. and the max-project-memory parameter has been defined as 3gigs .. is it normal or we are monitoring the project memory usage in wrong... (2 Replies)
Discussion started by: fugitive
2 Replies
9. Hardware
Can anyone tell me what the max num of physical memery depends? It's the bit number of the data bus?
How about the max number of the virtual memory? (1 Reply)
Discussion started by: cateran
1 Replies
10. AIX
Hi All,
Anyone know how to capture the nmon avg and max cpu and memory for one of the AIX server for Monthly Utilization Report purposes ?
Thanks.
---------- Post updated at 05:18 AM ---------- Previous update was at 05:07 AM ----------
if possible use shell script to count or sum... (6 Replies)
Discussion started by: ckwan
6 Replies
LEARN ABOUT NETBSD
munlock
MLOCK(2) BSD System Calls Manual MLOCK(2)
NAME
mlock, munlock -- lock (unlock) physical pages in memory
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/mman.h>
int
mlock(void *addr, size_t len);
int
munlock(void *addr, size_t len);
DESCRIPTION
The mlock system call locks into memory the physical pages associated with the virtual address range starting at addr for len bytes. The
munlock call unlocks pages previously locked by one or more mlock calls. The entire range of memory must be allocated.
After an mlock call, the indicated pages will cause neither a non-resident page nor address-translation fault until they are unlocked. They
may still cause protection-violation faults or TLB-miss faults on architectures with software-managed TLBs. The physical pages remain in
memory until all locked mappings for the pages are removed. Multiple processes may have the same physical pages locked via their own virtual
address mappings. A single process may likewise have pages multiply-locked via different virtual mappings of the same pages or via nested
mlock calls on the same address range. Unlocking is performed explicitly by munlock or implicitly by a call to munmap which deallocates the
unmapped address range. Locked mappings are not inherited by the child process after a fork(2).
Since physical memory is a potentially scarce resource, processes are limited in how much they can lock down. A single process can mlock the
minimum of a system-wide ``wired pages'' limit and the per-process RLIMIT_MEMLOCK resource limit.
Portable code should ensure that the addr and len parameters are aligned to a multiple of the page size, even though the NetBSD implementa-
tion will round as necessary.
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
mlock() will fail if:
[EAGAIN] Locking the indicated range would exceed either the system or per-process limit for locked memory.
[EINVAL] The length is negative; or the address or length given is not page aligned and the implementation does not round.
[ENOMEM] Some portion of the indicated address range is not allocated. There was an error faulting/mapping a page.
[EPERM] mlock() was called by non-root on an architecture where locked page accounting is not implemented.
munlock() will fail if:
[EINVAL] The length is negative; or the address or length given is not page aligned and the implementation does not round.
[ENOMEM] Some portion of the indicated address range is not allocated. Some portion of the indicated address range is not locked.
SEE ALSO
fork(2), mincore(2), mmap(2), munmap(2), setrlimit(2), getpagesize(3)
STANDARDS
The mlock() and munlock() functions conform to IEEE Std 1003.1b-1993 (``POSIX.1'').
HISTORY
The mlock() and munlock() functions first appeared in 4.4BSD.
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
February 28, 2011 BSD