0a91cdd486
The NICs overview table lists all supported features per driver. There was a single row for "Flow API", although rte_flow is composed of many items and actions. The row "Flow API" is replaced with two new tables for items and actions. Also, since rte_flow is not implemented in all drivers, it would be ugly to add empty sections in some files. That's why the error message for missing INI section is removed. The lists are sorted alphabetically. The extra files for some VF and vectorized data paths are not filled. Signed-off-by: Asaf Penso <asafp@nvidia.com> Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Kiran Kumar K <kirankumark@marvell.com> --- v6 changes: - rebase/update - remove deprecated shared action
43 lines
1.2 KiB
ReStructuredText
43 lines
1.2 KiB
ReStructuredText
.. SPDX-License-Identifier: BSD-3-Clause
|
|
Copyright 2016 6WIND S.A.
|
|
|
|
Overview of Networking Drivers
|
|
==============================
|
|
|
|
The networking drivers may be classified in two categories:
|
|
|
|
- physical for real devices
|
|
- virtual for emulated devices
|
|
|
|
Some physical devices may be shaped through a virtual layer as for
|
|
SR-IOV.
|
|
The interface seen in the virtual environment is a VF (Virtual Function).
|
|
|
|
The ethdev layer exposes an API to use the networking functions
|
|
of these devices.
|
|
The bottom half part of ethdev is implemented by the drivers.
|
|
Thus some features may not be implemented.
|
|
|
|
There are more differences between drivers regarding some internal properties,
|
|
portability or even documentation availability.
|
|
Most of these differences are summarized below.
|
|
|
|
More details about features can be found in :doc:`features`.
|
|
|
|
.. _table_net_pmd_features:
|
|
|
|
.. include:: overview_table.txt
|
|
|
|
.. Note::
|
|
|
|
Features marked with "P" are partially supported. Refer to the appropriate
|
|
NIC guide in the following sections for details.
|
|
|
|
.. include:: rte_flow_items_table.txt
|
|
|
|
.. include:: rte_flow_actions_table.txt
|
|
|
|
.. Note::
|
|
|
|
rte_flow actions marked with "I" can be indirect as well.
|