interprocess communication

Status
Not open for further replies.
B

banh

Advanced Member level 1
Joined
Dec 16, 2004
Messages
458
Helped
17
Reputation
34
Reaction score
5
Trophy points
1,298
Activity points
3,935
for very small & limited system (esp. small RAM), which methods are good for interprocess communication?:
- using shared variables with mutex.
- using mailboxes - similary to a queue with many producers and consumers.
..any other?
 

THis depends what and how you are going to pass data from one proess to another .
Queues are good for passing large sized data in form of messages (mailbox used if you have one message to be read before next will be put into queue) .Mutex is usefull when protecting access to the resources (if only one user could access to resource at a time) . Semaphores are usefull when dealing with resource allocation if you have certain amount of resources (let say buffers ) .
 

Share Memory would be a good idea if sync. is not an important issue.If sync. has to be consider i would prefer 2-way share memory access.

If there are a lot of client accessing for competition
i would suggest share memory with critical session or mutex or signal.

Regards
 

Shared memory is good idea

but if process is critical then use mutex
if sync is required then use semaphore

but it is very important to study time graph of your system at run time
this would give you a inside picture of various bottle necks if at all so you can decide and chose diffrent IPC for diffrent process

Added after 55 seconds:

Shared memory is good idea

but if process is critical then use mutex
if sync is required then use semaphore

but it is very important to study time graph of your system at run time
this would give you a inside picture of various bottle necks if at all so you can decide and chose diffrent IPC for diffrent process
 

Status
Not open for further replies.

Similar threads

Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…