Sponsored Content
Operating Systems AIX Regarding Upgrading RAM in AIX 6.1 Post 302893266 by zaxxon on Tuesday 18th of March 2014 08:26:35 AM
Old 03-18-2014
As a workaround this will work for some time, but the issue why you have memory problems might still show up, can just take longer until the RAM is used up. But that depends on what you are running and how the problems shows itself.
Though additional CPU units will not help with memory issues.

So as the others suggested, you should investigate what is the reason for your memory problem.

And as blackrageous asked, there is no need for so much paging space. I would go for a fix Paging Space size of 5GB or 10GB. When your system starts to use it, the performance will usually degrade enormous and so the goal is to avoid that before it happens.
 

10 More Discussions You Might Find Interesting

1. AIX

Upgrading AIX Unix

Hi all, I've got a question about an OS upgrade. I'm planning to do a upgrade from AIX UNIX 4.3.2 to 4.3.3 in a few weeks. I haven't got that much information. Could someone give me some general tips or hints, things I should think of before? Things I should know, or general errors. I know... (9 Replies)
Discussion started by: Erik Rooijmans
9 Replies

2. AIX

To find RAM Size in AIX as normal user?

Hi, Am jus trying to find the Total RAM Size of a AIX m/c (in MB)..svmon works perfectly for a superuser...But i want to achive this as a normal user...Please help me out with correct command.. Best Regards, Muthukumaran.M (3 Replies)
Discussion started by: muthukumaran13
3 Replies

3. Red Hat

red hat Linux 5.0 is detecting 3gb ram but physical ram is 16gb

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

4. AIX

Upgrading AIX 5.2 to AIX 6.1 - GCC compatibility

Hi All, We are in the processing of upgrading our AIX server OS from 5.2.0.0 to 6.1. And we have a set of highly critical running C applications in AIX box. I have a question like whether this upgradation of OS will affect any C code compilation and C runtime enviornment... how does AIX 6.1... (1 Reply)
Discussion started by: karthikc
1 Replies

5. AIX

Upgrading AIX from 5.3 to 6.1

Hi, I am having 2 Hard disk one for os and another for data,I would like to know for Upgrading AIX 5.3 to 6.1,wheather I have to varry off datavg while upgrading, or any other files needs to be backup. Please suggest Regards, Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies

6. AIX

Upgrading from native MPIO to SDDPCM AIX 6.1

We have AIX 6.1 system attached to SAN disks (DS4700 and DS8100) thru SVC. Initially when the system was I forgot to install sddpcm drivers. and wanted to know how can i go with the installation of the sddpcm drivers. My understandin going thru the manual ... (3 Replies)
Discussion started by: mk8570
3 Replies

7. AIX

Upgrading from aix 5.3 to ?

Hey guys, since AIX 5.3 reaches EOS on april 2012, I really need to update my systems asap. Any experience on upgrading directly to 7.1, with sap/db2/oracle? could do fresh installs and import my sap/db vgs, but this would be a lot of work cheers Funksen (4 Replies)
Discussion started by: funksen
4 Replies

8. AIX

New to AIX need help Installing/Upgrading Samba on AIX 7.1?

Hello, I am trying to update Samba on my AIX 7.1 system as there is an issues with it, the smbd process coredumps and I have had no luck figuring it out why. My approach is to try to re-install a newer samba and I have found the latest 3.x package for samba in ppc.rpm format at perlz.org ... (6 Replies)
Discussion started by: c3rb3rus
6 Replies

9. AIX

How can we re-mount the RAM disk automatically after the reboot on AIX?

Hi All, I was trying to know more about RAM disk concept in AIX. I found something on IBM site. I was able to create and use/delete RAM disk as per IBM instructions. But as you guys know, this RAM disk is a temporary storage. (*when ever we reboot the AIX LPAR, content/RAM disk will be... (4 Replies)
Discussion started by: System Admin 77
4 Replies

10. AIX

Upgrading to AIX 7 vs migrating

Hi all, I have this weird notion that upgrading the TL does not cause the machine to wipe, but upgrading a major version (from aix 6 to 7) means it's actually a fresh install and will wipe the date and i have to install the software again (TSM server, for instance). Trying to google it, i came... (3 Replies)
Discussion started by: tde3000
3 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)
All times are GMT -4. The time now is 11:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy