05-24-2013
Quote:
Originally Posted by
Chetanz
1) In the output of following command many processes are showing Pgsp>0; In that case can we say all the processes with Pgsp>0 are 'causing' the paging on system?
I am are these processes 'the cause'?
No, processes which does not active for a (long) time, will moved to the paging space device. At this time, where the VMM move the memory allocated by these process, You will see paging out operation. If this process is still inactive You will see only paging space used and no paging out or paging in operation. When this process becomes avtiv (eg. IO finished, no more lock on a requested resource, etc.) You will see paging in operations.
Quote:
Originally Posted by
Chetanz
2) Few processes are showing Pgsp>0 with "svmon" but with "ps aux" those are showing %MEM as 0.0 constantly Ex.PID= 5677206, below
what could be the reason?
Maybe this process is currently not activ. So have a look at the %CPU and TIME column for this process.
Have You tried to run NMON?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
Is there a paging utility in UNIX, when we can page some one for some condition
Best Regards
Omran (1 Reply)
Discussion started by: omran
1 Replies
2. AIX
This is my first post, and I am new to the UNIX world. Hopefully this question won't be too lame.
I know that I can use topas to see the paging space used by some processes. I would like to script something that can add up the paging space used by process owned by or associated with an... (1 Reply)
Discussion started by: alntht
1 Replies
3. Shell Programming and Scripting
I need a script which sends a mail when paging is happening and which process is causing paging? (5 Replies)
Discussion started by: jayaramanit
5 Replies
4. AIX
Hi,
I have paging size 2048M showed from topas and 10240M showed from "lsps -a", can anyone tell what is the difference? and how to change the PAGING SIZE (showed in topas) to 8192M?
Can you please tell in detail step?
Thanks!
Victor
#topas
Topas Monitor for host: egsprc01dev ... (10 Replies)
Discussion started by: victorcheung
10 Replies
5. Shell Programming and Scripting
how to get output of a file which is large screen by screen (1 Reply)
Discussion started by: mayur_verma
1 Replies
6. AIX
Hi ,
I have 8Gb memory in my JS21 server. When I run svmon it shows 3655Mb memory is utilized and 4344Mb free. I have configured 8Gb paging space and 14% is utilized which is 1Gb. I dont have memory issues but just want to know Why 1gb paging is utilized when my almost 4Gb real memory is free?... (6 Replies)
Discussion started by: vjm
6 Replies
7. AIX
I do have a friend who have this script already but lost it. Can you please help to give me a script that can capture the closed_wait on the stack and identify which process using it. I am thinking of using netstat and rmsock. (2 Replies)
Discussion started by: depam
2 Replies
8. BSD
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (0 Replies)
Discussion started by: naveeng
0 Replies
9. UNIX for Advanced & Expert Users
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (1 Reply)
Discussion started by: naveeng
1 Replies
10. UNIX for Advanced & Expert Users
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (6 Replies)
Discussion started by: naveeng
6 Replies
MLOCK(2) Linux Programmer's Manual MLOCK(2)
NAME
mlock - disable paging for some parts of memory
SYNOPSIS
#include <sys/mman.h>
int mlock(const void *addr, size_t len);
DESCRIPTION
mlock disables paging for the memory in the range starting at addr with length len bytes. All pages which contain a part of the specified
memory range are guaranteed be resident in RAM when the mlock system call returns successfully and they are guaranteed to stay in RAM until
the pages are unlocked by munlock or munlockall, until the pages are unmapped via munmap, or until the process terminates or starts another
program with exec. Child processes do not inherit page locks across a fork.
Memory locking has two main applications: real-time algorithms and high-security data processing. Real-time applications require determin-
istic timing, and, like scheduling, paging is one major cause of unexpected program execution delays. Real-time applications will usually
also switch to a real-time scheduler with sched_setscheduler. Cryptographic security software often handles critical bytes like passwords
or secret keys as data structures. As a result of paging, these secrets could be transfered onto a persistent swap store medium, where they
might be accessible to the enemy long after the security software has erased the secrets in RAM and terminated.
Memory locks do not stack, i.e., pages which have been locked several times by calls to mlock or mlockall will be unlocked by a single call
to munlock for the corresponding range or by munlockall. Pages which are mapped to several locations or by several processes stay locked
into RAM as long as they are locked at least at one location or by at least one process.
On POSIX systems on which mlock and munlock are available, _POSIX_MEMLOCK_RANGE is defined in <unistd.h> and the value PAGESIZE from <lim-
its.h> indicates the number of bytes per page.
NOTES
With the Linux system call, addr is automatically rounded down to the nearest page boundary. However, POSIX 1003.1-2001 allows an imple-
mentation to require that addr is page aligned, so portable applications should ensure this.
RETURN VALUE
On success, mlock returns zero. On error, -1 is returned, errno is set appropriately, and no changes are made to any locks in the address
space of the process.
ERRORS
ENOMEM Some of the specified address range does not correspond to mapped pages in the address space of the process or the process tried to
exceed the maximum number of allowed locked pages.
EPERM The calling process does not have appropriate privileges. Only root processes are allowed to lock pages.
EINVAL len was not a positive number.
CONFORMING TO
POSIX.1b, SVr4. SVr4 documents an additional EAGAIN error code.
SEE ALSO
mlockall(2), munlock(2), munlockall(2), munmap(2), setrlimit(2)
Linux 1.3.43 1995-11-26 MLOCK(2)