From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] ethdev: Clarify usage of TM node parent update API function Date: Tue, 31 Jul 2018 17:05:52 +0200 Message-ID: <1748890.xKDDESA46q@xps> References: <20180710153301.546-1-benjamin.h.shelton@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Ben Shelton To: Cristian Dumitrescu Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 4E43E98 for ; Tue, 31 Jul 2018 17:05:58 +0200 (CEST) In-Reply-To: <20180710153301.546-1-benjamin.h.shelton@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Cristian, review please? 10/07/2018 17:33, Ben Shelton: > The node parent update API function may be used to update the > priority/weight of an existing node. Update the documentation to > indicate that this use case is supported. > > Signed-off-by: Ben Shelton [...] > /** > * Traffic manager node parent update > * > + * This function may be used to move a node and its children to a different > + * parent. Additionally, if the new parent is the same as the current parent, > + * this function will update the priority/weight of an existing node. > + * > * Restriction for root node: its parent cannot be changed. > * > * This function can only be called after the rte_tm_hierarchy_commit()