05-06-2010
Any alternatives to IPC mechanism?
What if the operating systems would not use any ipc mechanism in order to exchange the datas with each other,which technique could be an alternative for messaging between the processes?Do you guys think using the vfork () system call to duplicate processes is a logical solution for this problem?
Last edited by helltrex; 05-06-2010 at 04:32 PM..
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a parent that is passing data to child A and then child A has to process it and pass to child B. I am able to pass the data to child A but am not able to pass it to child B. Child B seems to only be receiving the last data instead of the whole data.
I saw one example in a book but it uses... (1 Reply)
Discussion started by: scmay
1 Replies
2. Programming
Hi,
The description and the context of the mechanism that i require is as follows:
There is an application communicating with a protocol stack binary. There is a TCP socket communication between the two.
Now, the stack is pumping up data to the Application such that the receiving buffer of... (2 Replies)
Discussion started by: saptarshi
2 Replies
3. Programming
Hi! I'm trying to write this program: in my intentions it should get a message and send it to a second process (pid_upost), then to a third process (pid1, pid2, pid3, depending on the choice made when a new message is inserted). This program should write the message in a file (message1, message2 or... (1 Reply)
Discussion started by: Kaminski
1 Replies
4. Shell Programming and Scripting
I have a shell script.
How can use some kind of locking mechanism to ensure that the script is not being executed by two people
at the same time? (3 Replies)
Discussion started by: tjay83
3 Replies
5. AIX
Hi all,
on aix,whether have udev or devfs mechanism?
thanks! (4 Replies)
Discussion started by: anonys
4 Replies
6. Programming
OIOIC is a completely new object-oriented mechanism for the C programming language.
Please download the "OIOIC-Primer-2nd-Edition-English.tar.gz". (the English version of << OIOIC Primer >> )
http://code.google.com/p/oioic/downloads/list
Welcome your advice!
Using OIOIC, you can describe... (7 Replies)
Discussion started by: pervise.zhao
7 Replies
7. Solaris
I was asked to look into a problem with a Sun Netra 440 in another department. On the server in question, the relevant 'uname -a' information is, "SunOS host1 5.9 Generic_118558-16 sun4u sparc SUNW,Netra-440". That information aside, while the other admin is logged into the ALOM, these errors are... (0 Replies)
Discussion started by: Borealis
0 Replies
8. Programming
Suppose I have 5 independent process divided in two imaginay sets:
set1 set2
---------------------
p1 p3
| |
p2 p4
|
p5
The processes inside each set communicate mutually quite often.
I mean p1 and p2 communicate mutually quite often
Similarly p3, p4 and p5 communicate mutually... (2 Replies)
Discussion started by: rupeshkp728
2 Replies
LEARN ABOUT PLAN9
rendezvous
RENDEZVOUS(2) System Calls Manual RENDEZVOUS(2)
NAME
rendezvous - user level process synchronization
SYNOPSIS
#include <u.h>
#include <libc.h>
ulong rendezvous(ulong tag, ulong value)
DESCRIPTION
The rendezvous system call allows two processes to synchronize and exchange a value. In conjunction with the shared memory system calls
(see segattach(2) and fork(2)), it enables parallel programs to control their scheduling.
Two processes wishing to synchronize call rendezvous with a common tag, typically an address in memory they share. One process will arrive
at the rendezvous first; it suspends execution until a second arrives. When a second process meets the rendezvous the value arguments are
exchanged between the processes and returned as the result of the respective rendezvous system calls. Both processes are awakened when the
rendezvous succeeds.
The tag space is common to processes in the same file name space, so rendezvous only works between processes in the same file name space.
If a rendezvous is interrupted the return value is ~0, so that value should not be used in normal communication.
SOURCE
/sys/src/libc/9syscall
SEE ALSO
segattach(2), fork(2)
DIAGNOSTICS
Sets errstr.
BUGS
The correlation of rendezvous tags and file name space is a historical accident. If two unrelated processes happen to be in the same name
space and do a rendezvous, trouble will result. The solution is to call rfork(RFNAMEG) (see fork(2)) in programs that use rendezvous
unless they need to share the name space with their parent. This is especially important in Alef programs.
RENDEZVOUS(2)