[dpdk-dev] [PATCH] doc/tm: update support for pf only
Dumitrescu, Cristian
cristian.dumitrescu at intel.com
Mon Oct 15 17:52:35 CEST 2018
> -----Original Message-----
> From: Varghese, Vipin
> Sent: Monday, October 15, 2018 8:05 AM
> To: dev at dpdk.org; Dumitrescu, Cristian <cristian.dumitrescu at intel.com>
> Cc: Byrne, Stephen1 <stephen1.byrne at intel.com>; Mcnamara, John
> <john.mcnamara at intel.com>; Doherty, Declan
> <declan.doherty at intel.com>; Varghese, Vipin <vipin.varghese at intel.com>
> Subject: [PATCH] doc/tm: update support for pf only
>
> Documentation is updated to highlight the support for DPDK ethernet
> interface for Traffic Manager is currently limited to PF only.
>
> Signed-off-by: Vipin Varghese <vipin.varghese at intel.com>
> ---
> doc/guides/prog_guide/traffic_management.rst | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/prog_guide/traffic_management.rst
> b/doc/guides/prog_guide/traffic_management.rst
> index 98ac4310b..e6304d372 100644
> --- a/doc/guides/prog_guide/traffic_management.rst
> +++ b/doc/guides/prog_guide/traffic_management.rst
> @@ -16,7 +16,8 @@ is agnostic of the underlying HW, SW or mixed HW-SW
> implementation.
> Main features:
>
> * Part of DPDK rte_ethdev API
> -* Capability query API per port, per hierarchy level and per hierarchy node
> +* Capability query API per port, per hierarchy level and per hierarchy node
> on
> + PF ethernet devices
> * Scheduling algorithms: Strict Priority (SP), Weighed Fair Queuing (WFQ)
> * Traffic shaping: single/dual rate, private (per node) and
> shared (by multiple nodes) shapers
> @@ -221,3 +222,4 @@ thus operations such as node add/delete, node
> suspend/resume, parent node
> update, etc., can be invoked after the Ethernet port has been started,
> subject
> to the specific implementation supporting them. The set of dynamic updates
> supported by the implementation is advertised through the port capability
> set.
> +TM features are currently supported for PF Ethernet devices.
> --
> 2.17.1
NAK.
The API is agnostic of the nature of ethdev port. The API is the same, whether it is called for a PF port or for a VF port.
More information about the dev
mailing list