Changeset b412038 in rtems-docs for networking/network_task_structure.rst


Ignore:
Timestamp:
04/11/16 03:53:58 (7 years ago)
Author:
Chris Johns <chrisj@…>
Branches:
4.11, 5, am, master
Children:
bc37517
Parents:
ea0777e
git-author:
Chris Johns <chrisj@…> (04/11/16 03:53:58)
git-committer:
Amar Takhar <verm@…> (05/03/16 00:51:27)
Message:

Clean up and review of Networking User Guide.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • networking/network_task_structure.rst

    rea0777e rb412038  
     1.. COMMENT: Written by Eric Norum
     2.. COMMENT: COPYRIGHT (c) 1988-2002.
     3.. COMMENT: On-Line Applications Research Corporation (OAR).
     4.. COMMENT: All rights reserved.
     5
    16Network Task Structure and Data Flow
    27####################################
    38
    4 A schematic diagram of the tasks and message *mbuf* queues in a
    5 simple RTEMS networking application is shown in the following
    6 figure:
     9A schematic diagram of the tasks and message *mbuf* queues in a simple RTEMS
     10networking application is shown in the following figure:
    711
    812.. image:: images/networkflow.jpg
    913
    1014
    11 The transmit task  for each network interface is normally blocked waiting
    12 for a packet to arrive in the transmit queue.  Once a packet arrives, the
    13 transmit task may block waiting for an event from the transmit interrupt
    14 handler.  The transmit interrupt handler sends an RTEMS event to the transmit
    15 task to indicate that transmit hardware resources have become available.
     15The transmit task for each network interface is normally blocked waiting for a
     16packet to arrive in the transmit queue.  Once a packet arrives, the transmit
     17task may block waiting for an event from the transmit interrupt handler.  The
     18transmit interrupt handler sends an RTEMS event to the transmit task to
     19indicate that transmit hardware resources have become available.
    1620
    17 The receive task for each network interface is normally blocked waiting
    18 for an event from the receive interrupt handler.  When this event is received
    19 the receive task reads the packet and forwards it to the network stack
    20 for subsequent processing by the network task.
     21The receive task for each network interface is normally blocked waiting for an
     22event from the receive interrupt handler.  When this event is received the
     23receive task reads the packet and forwards it to the network stack for
     24subsequent processing by the network task.
    2125
    22 The network task processes incoming packets and takes care of
    23 timed operations such as handling TCP timeouts and
    24 aging and removing routing table entries.
     26The network task processes incoming packets and takes care of timed operations
     27such as handling TCP timeouts and aging and removing routing table entries.
    2528
    26 The 'Network code' contains routines which may run in the context of
    27 the user application tasks, the interface receive task or the network task.
    28 A network semaphore ensures that
    29 the data structures manipulated by the network code remain consistent.
    30 
    31 .. COMMENT: Written by Eric Norum
    32 
    33 .. COMMENT: COPYRIGHT (c) 1988-2002.
    34 
    35 .. COMMENT: On-Line Applications Research Corporation (OAR).
    36 
    37 .. COMMENT: All rights reserved.
    38 
     29The 'Network code' contains routines which may run in the context of the user
     30application tasks, the interface receive task or the network task.  A network
     31semaphore ensures that the data structures manipulated by the network code
     32remain consistent.
Note: See TracChangeset for help on using the changeset viewer.