Bonding was the only in-tree net PMD without an entry in doc/guides/nics/features, so it did not appear in the driver overview table.
Signed-off-by: Stephen Hemminger <[email protected]> --- doc/guides/nics/features/bonding.ini | 40 ++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 doc/guides/nics/features/bonding.ini diff --git a/doc/guides/nics/features/bonding.ini b/doc/guides/nics/features/bonding.ini new file mode 100644 index 0000000000..27560f63c7 --- /dev/null +++ b/doc/guides/nics/features/bonding.ini @@ -0,0 +1,40 @@ +; +; Supported features of the 'bonding' network poll mode driver. +; +; Refer to default.ini for the full list of available PMD features. +; +[Features] +Speed capabilities = Y +Link speed configuration = Y +Link status = Y +Link status event = Y +Fast mbuf free = Y +MTU update = Y +Promiscuous mode = Y +Allmulticast mode = Y +Unicast MAC filter = Y +RSS hash = Y +RSS key update = Y +RSS reta update = Y +VLAN filter = Y +Basic stats = Y +Extended stats = Y +FreeBSD = Y +Linux = Y +ARMv8 = Y +Power8 = Y +x86-32 = Y +x86-64 = Y +Usage doc = Y + +; Flow rules are passed through to the members, so the usable items and +; actions are those common to all of them. Only the types named by the +; bonding driver itself are listed here: eth and queue are used for the +; mode 4 dedicated LACP queue, and count is the one action that +; bonding aggregates across members on query. +[rte_flow items] +eth = P + +[rte_flow actions] +count = P +queue = P -- 2.53.0
