Is Message passing good approach for multi-threaded applications?

hi all,

I am currently developing an embedded protocol converter.In this
application there are 16 serial ports and 2 Ethernet ports.There are
16 threads for each serial port and also there is a network server
which accepts connections from LAN. so there is a thread per each
connection.There are also some threads for other tasks like
application management, time synchronization etc. As a solution to the
problem of communication between these threads i choose message
passing.There are 2 queues.One for requests and one for responses. LAN
threads put messages into request queue and other threads put replies
into response queue. Because our system has a CPU with 500MHz speed
(ARM9) i was concern if this approach can satisfy our
requirement.Each request and subsequent response should take only 200
ms. Does this architecture ( message passing as a communication bus )
good or there are some other approaches? Any guide,URL, book,
experience would appreciated.

Thanks in advance
Behzad
.

Relevant Pages

  • Is Message passing good approach for multi-threaded applications?
    ... application there are 16 serial ports and 2 Ethernet ports.There are ... threads put messages into request queue and other threads put replies ... requirement.Each request and subsequent response should take only 200 ...
    (comp.os.linux.misc)
  • Is Message passing good approach for multi-threaded applications?
    ... application there are 16 serial ports and 2 Ethernet ports.There are ... threads put messages into request queue and other threads put replies ... requirement.Each request and subsequent response should take only 200 ...
    (comp.unix.programmer)
  • Is Message passing good approach for multi-threaded applications?
    ... application there are 16 serial ports and 2 Ethernet ports.There are ... threads put messages into request queue and other threads put replies ... requirement.Each request and subsequent response should take only 200 ...
    (comp.programming.threads)
  • Re: W2K3 IIS 6.0 ASP.NET Requests Per Second Limits?
    ... allow the page to tell ASP.Net "don't send a response yet until I tell ... this request is "leaked" and will never ... It is when the callback executes with both the async function call ... The thread executing code literally calls into Function1, execute code, ...
    (microsoft.public.inetserver.iis)
  • Re: W2K3 IIS 6.0 ASP.NET Requests Per Second Limits?
    ... >> The way I understand async programming is if u need to do other ... >> request to webservice nothing more can be done until the result ... > The thread executing code literally calls into Function1, ... > the act of sending back the response using data that has been ...
    (microsoft.public.inetserver.iis)