08-23-2013
The more highmem exists the more memory pressure can be expected in lowmem.
This will result in sudden short-living performance decrease or memory initializing failures.
With SuSE kernels the OOM killer will be invoked before total memory isused up.
For more than 8 GB RAM use a 64 bit kernel!
10 More Discussions You Might Find Interesting
1. AIX
Hello AIX gurues...
In order to present the statistics of real memory usage I need to know how much real memory is used by the AIX 5L kernel. No the exact figures of course but some close to the reality.
The AIX is running in a 7GB real machine, it has a HACMP configuration and my concern is... (1 Reply)
Discussion started by: daniels
1 Replies
2. UNIX for Dummies Questions & Answers
Hellp all,
if there is 3G memory in my Unix server I want to know if all the 3G space can be used by ong sigle process. As i know, in Windows, one process can only access at most 1G memory despite there is probably more than 1G memory is equipped. (1 Reply)
Discussion started by: cy163
1 Replies
3. Linux
ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before?
I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system.
Please Help... (2 Replies)
Discussion started by: dave043
2 Replies
4. Ubuntu
I have a customer with an HP DL380 G4 server running Redhat 2.1 AS that has 4GB memory installed. They want to upgrade in the server to the maximum of 12GB using (6) 2GB DIMMs. I can do this for them, but I read somewhere that Redhat 2.1 has an upper memory limit. Or you need a kernel patch to use... (2 Replies)
Discussion started by: Cbish68
2 Replies
5. Shell Programming and Scripting
Is there an input file memory limit for awk?
I have a 38Mb text file that I am trying to print out certatin lines and add a string to the end of that line.
When I excute the script on the 38Mb file the string I am adding is put on a new line. If I do the same with a smaller file the... (3 Replies)
Discussion started by: cold_Que
3 Replies
6. Shell Programming and Scripting
Hi, I have .sh script running php script with "php". When I run php script from web browser, it is running without errors. When I run it from .sh script, I am getting "memory exhausted". It seems to me that running php from .sh does not respect php.ini or have its own setting. So, how can I set... (0 Replies)
Discussion started by: LukasB
0 Replies
7. AIX
Greetings -
I'm porting a C application to an AIX (6.1) system, and have bumped into the limits AIX imposes on memory allocation, namely the default limit of 256MB for a process. I'm aware of the compilation flag that allows an application to gain access to up to 8 memory segments (each 256MB,... (4 Replies)
Discussion started by: traviswheeler
4 Replies
8. UNIX for Dummies Questions & Answers
Hi everyone,
I am running Debian Wheezy 7.2 with a 3.2.0-4-686-pae kernel. There are a couple of virtual files and directories in /proc I can't seem to find much information about. I am aware that some of them might be legacy, though. Anyway, here they are:
acpi: according to this link, this... (2 Replies)
Discussion started by: gacanepa
2 Replies
9. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
10. Red Hat
Hi all !
I'm new in this site, so sorry if this question is into wrong place.
How can I limit cpu/core and memory usage by user?
System: RedHat Ent. Linux. 6.4
Tks, (4 Replies)
Discussion started by: Tiago
4 Replies
LEARN ABOUT HPUX
aio_physmem_pct
aio_physmem_pct(5) File Formats Manual aio_physmem_pct(5)
NAME
aio_physmem_pct - percentage of physical memory lockable for request call-back POSIX asynchronous I/O operations
VALUES
Failsafe
Default
Allowed values
The minimum value allowed is The maximum value allowed is
Specify a positive integer value.
DESCRIPTION
This parameter places a limit on how much system memory can be locked by the total number of POSIX asynchronous I/O operations that are in
progress at any given time.
It is important to be aware that an operation remains on the active queue and memory is not released, even if the operation is complete,
until it is properly terminated by an call for that operation.
The value of represents a percentage of system memory, and the limit it controls will adjust with Online Addition or Deletion of physical
memory (OL*), as appropriate.
Asynchronous I/O operations that use a request-and-callback mechanism for I/O must be able to lock the memory they are using. The request-
and-callback mechanism is used only if the device drivers involved support it. Memory is locked only while the I/O transfer is in
progress.
imposes a system-wide limit on lockable physical memory. A per-process lockable-memory limit can also be self-imposed by using the system
call within the application program (see setrlimit(2)).
Who Is Expected to Change This Tunable?
System administrators that run applications requiring heavy usage of POSIX AIO to file systems.
Restrictions on Changing
This tunable is dynamic. Any changes to the value of this tunable will take effect immediately without requiring system reboot.
The amount of memory that can be locked under the limit imposed by cannot exceed the total system wide lockable memory limit imposed by
The limit dictated by this tunable, is checked individually for each incoming request for file system or devices that support the
request/callback mechanism. When tuning to a lower value, the new limit will be immediately enforced for all new requests, and the tuning
will succeed even if the current usage count is higher. The usage will then gradually adjust to the new limit.
When Should the Value of This Tunable Be Raised?
On a large server it is better to increase to higher values (up to 50).
What Other Tunables Should Be Changed at the Same Time as This One?
The total amount of memory that can be locked at any given time for any reason, not just for asynchronous I/O, is controlled by the system-
wide limit Other system activity, including explicit memory locking with the and/or interfaces can also affect the amount of lockable mem-
ory at any given time.
There is no kernel parameter named but there is a parameter named that affects it. The value of is determined by subtracting the value of
from the amount of system memory available after system startup. During startup, the system displays on the system console the amount of
its lockable memory (along with available memory and physical memory). These values can be retrieved while the system is running with com-
mand.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
SEE ALSO
kctune(1M), sam(1M), gettune(2), settune(2), aio(5), aio_return(2), dmesg(1M), mlock(2), plock(2), getrlimit(2), setrlimit(2), unlock-
able_mem(5).
Tunable Kernel Parameters aio_physmem_pct(5)