Task design considerations for a multilayer protocol stack
- From: arut@xxxxxxxx
- Date: Tue, 30 Oct 2007 04:13:04 -0700
Hi,
If I need to design a system using Vxworks tasks with multiple
applications talking to a middle abstract layer with a drivers below
the middle one, how do I decide if I need a single task or multiple
tasks at the middle layer. Let us say there are 3 apllications app1,
app2,app3 which need to communicate with a middle layer in both
directions(send/recv information). The middle layer in turn interacts
with a lower layer with 2 drivers(again send/recv).
How many tasks would be needed in middle layer and what IPC mechanism
would they use and how many.
For example will each application use 2 queues (one for each
direction) or just a single queue.
I would also like to know on what basis would I determine the number
of tasks required in a system. Is there any guidleline for identifying
what/how much should be done in a single task and when we should go
for multiple tasks.
Please explain.
Thanks,
asm
.
- Follow-Ups:
- Prev by Date: Re: not getting vxWorks prompt
- Next by Date: Predefining Ip Address to multiple END devices in BSP
- Previous by thread: gcc intrinsic
- Next by thread: Re: Task design considerations for a multilayer protocol stack
- Index(es):
Relevant Pages
|