Sponsored Content
Full Discussion: posix ipc message queue
Operating Systems HP-UX posix ipc message queue Post 302072035 by cadanir on Wednesday 26th of April 2006 01:57:46 PM
Old 04-26-2006
posix ipc message queue

Hello,

My question is related to "pipcs -qa" command under HP-UX 11i PA-RISC 64 bits.

We have a little C program that creates posix ipc message queues using the mq_open() system function.

The program fail with 'No space left on device' error when we create big queues. What is the system limit of the size of all queues ?

If we calculates the sum of all the MNUM*QBYTES columns in the output of 'pipcs -qa' the error arrive when we are close to 860 or 900 Mbytes.

Is there a way to go beyond this amount of memory ?

How the system actually allocate the memory when we create a posix queue of 1024 bytes for a message and for example 100000 as the max number of messages ? Are the 1024 * 100000 bytes allocated when the queue is created or at usage time that is when we really put some messages on the queue ?

Is this related to the fact that HP-UX divide his memory space into 4 quadrants of 1GB each ? Is there a workaround ?

I already compiled the program using the 64 bit options of the K&R
style "bundled" compiler, I also tried 'setmemwindow' without success...

I'm not sure if posix IPC message queues are implemented using the mmap() function, if it is, then what is the max. shared memory size of mmap() ?

I also failed to convince users not to use so big queues...

If we cannot go beyond 900 Mbytes for the size of all queues we are planning to use something else like Java JMS or MQseries or a database ...


Thanks for your advice (and for reading this long post),

Cengiz ADANIR

Last edited by cadanir; 04-27-2006 at 09:21 AM..
 

10 More Discussions You Might Find Interesting

1. Programming

POSIX Message Queue - Settings

How can I increase the POSIX Msg Q parameter SC_MQ_PRIO_MAX? The maximum is defined as 32. Can I increase the number? If so, how? Deepa (0 Replies)
Discussion started by: Deepa
0 Replies

2. UNIX for Dummies Questions & Answers

Posix vs System V IPC quesions

What are the differences/similarities between posix and system V ipc and their mechanisms? also, why is system v only limited to inter-process communication on a single node? thanks (0 Replies)
Discussion started by: jsimpson
0 Replies

3. Linux

POSIX message queue size

Hi all, Please tell me how to change POSIX message queue maximum size? "ulimit" is not a solution because it controls shell resources. But i need to control queue size before login in and starting the shell. It is needed to limit queue size for applications started before login in. Sorry for my... (7 Replies)
Discussion started by: Vourhey
7 Replies

4. Programming

How to limit max no of message in a posix message queue

Hii can anyone pls tell how to limit the max no of message in a posix message queue. I have made changes in proc/sys/fs/mqueue/msg_max But still whenever i try to read the value of max. message in the queue using attr.mq_curmsgs (where struct mq_attr attr) its giving the default value as 10.... (0 Replies)
Discussion started by: mohit3884
0 Replies

5. Programming

IPC - queue problems

Hi, I´m having a lot of problems when working with message queues, both on HP-UX Systems and Sun Solaris. When we fill a queue with a messages, the system hangs and locks everything that relies on the use of IPC resources. Anyone knows how to eliminate this problem? Thanks, Haroldo Teixeira (2 Replies)
Discussion started by: haroldo
2 Replies

6. UNIX for Dummies Questions & Answers

IPC Message Queue. msgrcv doesnt work..

Hi everybody, this is the situation. there is a programm XYZ which opens a message queue with the key 47110815 and waits for a SIGUSR1. After receiving this signal it sends a message with type 100 and a number (as ASCII) in the message-body. I have to write a prog which frist sends the... (1 Reply)
Discussion started by: daredevil82m
1 Replies

7. Programming

kill() function problem in client-server ipc message using 2 FIFOs

I want to have a message send & receive through 2 uni-direction FIFO Flow of data FIFO1 stdin--->parent(client) writefd--->FIFO1-->child(server) readfd FIFO2 child(server) writefd2---->FIFO2--->parent(client) readfd2--->stdout I need to have boundary structed message... (3 Replies)
Discussion started by: ouou
3 Replies

8. Programming

Please help:program hang stuck there signal handling on POSIX Message Queue UNIX C programming

in a single main() function,so need signal handling. Use Posix Message Queue IPC mechanism , can ignore the priority and other linked list message,to implement the scenario: client:Knock Knock server:who's there client: Eric Server:Eric,Welcome. client:exit all process terminated ... (1 Reply)
Discussion started by: ouou
1 Replies

9. Programming

POSIX Message Queue Memory Allocation

Hi, I wanted to know whether the POSIX message queues are statically allocated memory by the kernel based on the parameters specified in the open or as and when we send messages, memory are allocated? Does the kernel reserve the specified memory for the message queue irrespective of whether... (1 Reply)
Discussion started by: sumtata
1 Replies

10. Programming

POSIX message queue mq_open directory

hello, I try to test the POSIX mq_open function on book unp like below: #include "unpipc.h" # include <mqueue.h> int main(int argc, char **argv) { int c, flags; mqd_t mqd; flags = O_RDWR | O_CREAT; while ((c = getopt(argc, argv, "e")) != -1) { ... (3 Replies)
Discussion started by: anpufeng
3 Replies
ipcs(1) 						      General Commands Manual							   ipcs(1)

NAME
ipcs - report status of interprocess communication facilities SYNOPSIS
core] namelist] DESCRIPTION
displays certain information about active interprocess communication facilities. With no options, displays information in short format for the message queues, shared memory segments, and semaphores that are currently active in the system. Options The following options restrict the display to the corresponding facilities. (none) This is equivalent to Display information about active shared memory segments. Display information about active message queues. Display information about active semaphores. The following options add columns of data to the display. See "Column Description" below. (none) Display default columns: for all facilities: Display all columns, as appropriate. This is equivalent to Display largest-allowable-size information: for message queues: for shared memory segments: for semaphores: Display creator's login name and group name: for all facilities: Display information on outstanding usage: for message queues: for shared memory segments: Display process number information: for message queues: for shared memory segments: Display time information: for all facilities: for message queues: for shared memory segments: for semaphores: The following options redefine the sources of information. Use core in place of core can be a core file or a directory created by or Use file namelist or the namelist within core in place of It opens a crash dump for reading. Please refer to cr_open(3) for more details. Column Descriptions The column headings and the meaning of the columns in an listing are given below. The columns are printed from left to right in the order shown below. Facility type: Shared memory segment Message queue Semaphore The identifier for the facility entry. The key used as an argument to or to create the facility entry. (Note: The key of a shared memory segment is changed to when the segment has been removed until all processes attached to the segment detach it.) The facility access modes and flags: The mode consists of 11 characters that are interpreted as follows: The first two characters can be: A process is waiting on a A process is waiting on a The associated shared memory segment has been removed. It will disappear when the last process attached to the segment detaches it. The associated shared memory segment is to be cleared when the first attach is executed. The corresponding special flag is not set. The next 9 characters are interpreted as three sets of three characters each. The first set refers to the owner's permissions, the next to permissions of others in the group of the facility entry, and the last to all others. Within each set, the first character indicates permission to read, the second character indicates permission to write or alter the facility entry, and the last character is currently unused. Read permission is granted. Write permission is granted. Alter permission is granted. The indicated permission is not granted. The login name of the owner of the facility entry. The group name of the group of the owner of the facility entry. The login name of the creator of the facility entry. The group name of the group of the creator of the facility entry. The number of bytes in messages currently outstanding on the associated message queue. The number of messages currently outstanding on the associated message queue. The maximum number of bytes allowed in messages outstanding on the associated message queue. The process ID of the last process to send a message to the associated message queue. The process ID of the last process to receive a message from the associated message queue. The time the last message was sent to the associated message queue. The time the last message was received from the associated message queue. The time when the associated facility entry was created or changed. The number of processes attached to the associated shared memory segment. The size of the associated shared memory segment. The process ID of the creating process of the shared memory segment. The process ID of the last process to attach or detach the shared memory segment. The time the last attach was completed to the associated shared memory segment. The time the last detach was completed on the associated shared memory segment. The number of semaphores in the set associated with the semaphore entry. The time the last semaphore operation was completed on the set associated with the semaphore entry. WARNINGS
produces only an approximate indication of actual system status because system processes are continually changing while is acquiring the requested information. Do not rely on the exact field widths and spacing of the output, as these will vary depending on the system, the release of HP-UX, and the data to be displayed. FILES
Kernel virtual memory Group names User names System namelist SEE ALSO
msgop(2), semop(2), shmop(2). STANDARDS CONFORMANCE
ipcs(1)
All times are GMT -4. The time now is 11:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy