/**
* Ethernet framing overhead including the Frame Check Sequence (FCS) field.
* Useful when FCS is generated and added at the end of the Ethernet frame on
- * TX side without any SW intervention.
+ * Tx side without any SW intervention.
*
* One of the typical values for the pkt_length_adjust field of the shaper
* profile.
* the lowest weight. For each SP priority, the WFQ weight mode can be set as
* either byte-based or packet-based.
*
- * Each leaf node sits on top of a TX queue of the current Ethernet port. Hence,
+ * Each leaf node sits on top of a Tx queue of the current Ethernet port. Hence,
* the leaf nodes are predefined, with their node IDs set to 0 .. (N-1), where N
- * is the number of TX queues configured for the current Ethernet port. The
+ * is the number of Tx queues configured for the current Ethernet port. The
* non-leaf nodes have their IDs generated by the application.
*/
struct rte_tm_node_params {
/**
* Traffic manager get number of leaf nodes
*
- * Each leaf node sits on on top of a TX queue of the current Ethernet port.
+ * Each leaf node sits on top of a Tx queue of the current Ethernet port.
* Therefore, the set of leaf nodes is predefined, their number is always equal
- * to N (where N is the number of TX queues configured for the current port)
+ * to N (where N is the number of Tx queues configured for the current port)
* and their IDs are 0 .. (N-1).
*
* @param[in] port_id
* Traffic manager node ID validate and type (i.e. leaf or non-leaf) get
*
* The leaf nodes have predefined IDs in the range of 0 .. (N-1), where N is
- * the number of TX queues of the current Ethernet port. The non-leaf nodes
+ * the number of Tx queues of the current Ethernet port. The non-leaf nodes
* have their IDs generated by the application outside of the above range,
* which is reserved for leaf nodes.
*
*
* This function has to be called for both leaf and non-leaf nodes. In the case
* of leaf nodes (i.e. *node_id* is within the range of 0 .. (N-1), with N as
- * the number of configured TX queues of the current port), the leaf node is
+ * the number of configured Tx queues of the current port), the leaf node is
* configured rather than created (as the set of leaf nodes is predefined) and
* it is also connected as child of an existing node.
*