diff options
| author | Joel Sherrill <joel@rtems.org> | 2016-10-28 12:21:15 -0500 |
|---|---|---|
| committer | Joel Sherrill <joel@rtems.org> | 2016-10-28 12:22:02 -0500 |
| commit | 53d00e6a43b2934363dcf4d969909ea20b3da311 (patch) | |
| tree | 8e401a09f797ea4b8eb4ea668ef53dae78827553 /networking/network_task_structure.rst | |
| parent | dec_21140.rst: Correct path to image (diff) | |
| download | rtems-docs-53d00e6a43b2934363dcf4d969909ea20b3da311.tar.bz2 | |
dec_21140.rst, network_task_structure.rst: Change image to figure
Diffstat (limited to '')
| -rw-r--r-- | networking/network_task_structure.rst | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/networking/network_task_structure.rst b/networking/network_task_structure.rst index 1dae210..51bccd5 100644 --- a/networking/network_task_structure.rst +++ b/networking/network_task_structure.rst @@ -11,8 +11,9 @@ Network Task Structure and Data Flow A schematic diagram of the tasks and message *mbuf* queues in a simple RTEMS networking application is shown in the following figure: -.. image:: ../images/networking/networkflow.jpg - +.. figure:: ../images/networking/networkflow.jpg + :align: center + :alt: Network Flow The transmit task for each network interface is normally blocked waiting for a packet to arrive in the transmit queue. Once a packet arrives, the transmit |