Hi,
I have HP-UX 11i v3 running on ia64. One of my application is 32-bit and I want to increase the memory allocation of this file upto 2GB. I am contentiously receiving an error message of Out of Memory.
Can you please explain the procedure what kernel configuration( like maxdsize or maxdsize_64) i need to set and also do i need to set anything on the application binary ?
Thanks in advance.
My file chatr is as follows
Last edited by jim mcnamara; 08-30-2012 at 02:49 PM..
Hi folks,
We are using following listed configurations for a particular application.
HP-UX 11i
Sun Java 2 SDK Standard Edition 1.4.1 (version shipped with WebLogic 8)
Oracle 9i Release 2 (Oracle 9.2.0)
BEA WebLogic Server 8.1 SP3
It seems a memory leak when we use above configurations.... (1 Reply)
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)
Hi all,
I have a HP-UX Server with 4 gigabytes of physical RAM. When I use the 'Glance' utility to see what my memory utilization is, my memory usage shows up maxed out at 99%. I shut off all the known processes that I'm running on that box and the memory utilization is still at 78% (with Swap... (1 Reply)
How can i Globally set the maximum core memory a single process can take. IE, i want to set that no single process may get more than 11GB.
I am running red hat enterprise unix 4. (9 Replies)
Hi everyone,
I'm not new to C programming, but I'm having question regarding the memory allocation of a pointer variable which, for instance, will be declared in main(), but its memory will be allocated in subroutine.
To clearify my question, I provide a small working example:
#include... (1 Reply)
Hi Experts
I need some help in static memory allocation in C. I have a program in which I declared 2 variables, one char array and one integer. I was little surprised to see the addresses of the variables.
First:
int x;
char a;
printf("%u %u\n', &x, a);
I got the addresses displayed... (2 Replies)
Hello Guys
I have a small confusion in the dynamic memory allocation concept.
If we declare a pointer say a char pointer, we need to allocate adequate memory space.
char* str = (char*)malloc(20*sizeof(char));
str = "This is a string";
But this will also work.
char* str = "This... (2 Replies)
When we dynamically allocate the memory say 100 integers say
int *x = new int(1000);
then does entire chunk of memory gets allocated at once after the completion of the statement?
I mean will the the concept of page fault come into picture over here? (3 Replies)
I want to run a C program on my linux machine. I want to allocate specific heap size for that process (C program) to run.
How can I do that?
I know in Java same can be done using -Xmx option.
There may be some option which I can specify in the C program like Java or may be in linux process. (8 Replies)
Discussion started by: Ankur Goyal
8 Replies
LEARN ABOUT DEBIAN
pvm_shmd
PVM_SHMD(1PVM) PVM Version 3.4 PVM_SHMD(1PVM)NAME
pvm_shmd - PVM shared memory(2) daemon
SYNOPSIS
pvm_shmd [ -options ] [ hostfile ]
DESCRIPTION
Pvm_shmd is a daemon process which maintains and handles the usage of shared memory resources (memory segments, semaphores, message queues)
on a particular PVM host. One pvm_shmd must run on each host in a virtual machine that wants to use the shmd shared memory message passing
layer. The shmd message passing layer allows local processes to a host to use shared memory for message passing on that host ONLY. See the
shmd directory README for further notes and restrictions.
The daemon can be started manually as with any other PVM task. Only one pvm_shmd can be active per host. If the pvm_shmd detects another
pvm_shmd it will shutdown.
The pvm_shmd can be killed from the PVM console by using the reset command. Local and remote pvm_shmds can also be started from the PVM
console program pvm.
The name of the daemon executable is pvm_shmd.
Shared Resource Usage
The pvm_shmd will attempt to create upto MAXSEG shared memory segments of upto MAXPAGES memory pages in size. The size of each memory page
is architecture dependent(see getpagesize(3C)). The segments are then numbered 0..N-1 where N is the number of segments created. The
first segement(0) has the shared memory control structure placed in its head. This structure allows alien processes to located the other
shared memory segments and any required controlling information.
The message passing layer, allocates memory from these segments asynchronously without any interaction with the pvm_shmd using semaphores
to protect data during updates to any associated structures. For each segment there is an associated page map of which processes have cur-
rently locked a page. Each page map for a segment has a separate semaphore protecting it. The semaphores are accessed with the SEM_UNDO
flag set so that if a process holding a semaphore should die, the OS (should) reset the semaphore automatically, thus allowing any wait-
ing/blocked processes to continue.
The pvm_shmd only maintains the segments and their allocation page map(s). Thus if a process allocated pages in a segment and then exits,
it is the pvm_shmd that detects this and then frees the allocated pages.
The pvm_shmd can have its status checked at any time by using the pvm_shmd_stat process to kick it into reporting onto either stdio or the
pvm log file (pvml.uid) its internal state.
The shared memory and all associated processes can be cleared by sending the pvm_shmd a HUP signal.
Sending the pvm_shmd a TERM signal will just cause it to clear any shared resources and then exit.
The pvm_shmd cannot catch the KILL signal.
If the pvm_shmd is killed without clearing all of its shared resources these can be cleared by calling ipcfree which resides in the
pvm3/lib directory.
Message Passing using SHMD
The pvm_shmd handles resources that are used by special versions of pvm_psend() and pvm_precv() stored in the libpvmshmd.a library. Thus to
use these facilities, applications have to link to this library instead of the usual libpvm3.a library.
OPTIONS
The following options may be specified on the command line when starting the pvm_shmd:
-debug=level
Sets the pvm_shmd debug level. Used to debug the pvm_shmd or libpvmshmd (not intended to be used to debug application programs).
-maxsegs=maxsegs
Sets the maximum number of segments that the pvm_shmd can create. This is used to over-ride the compiled in value from shmd.h. Note
that the value cannot be above the MAXSEGS in the shmd.h file.
-maxpages=maxpages
Sets the maximum segment size to maxpages pages of memory. This value cannot be above the compiled value MAXPAGES in shmd.h or the
actual OS defined limit.
NOTES
Remember that pvm_shmd allocated memory from the VM available on the machine. Allocating more segements improves performance as there is
less sharing of segments (semaphores for their page maps). Although you must remember to leave some memory available for normal program and
OS system usage, as the pvm_shmd allocated memory is *ONLY* used for message passing.
FILES
$PVM_ROOT/lib/$PVM_ARCH/pvm_shmd PVM shared memory daemon executable
$PVM_ROOT/shmd/shmd.h Shared Memory hard limits header file
/tmp/pvml.uid Pvmd runtime error log
SEE ALSO pvm(1PVM), pvmd(1PVM), getpagesize(3C), ipcs(1), msgctl(2), semctl(2), shmctl(2), signal(5)G.E.Fagg 11 March, 1999 PVM_SHMD(1PVM)