From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <cristian.dumitrescu@intel.com> Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 3C7A62C5 for <dev@dpdk.org>; Tue, 31 Jul 2018 17:09:27 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Jul 2018 08:09:26 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,427,1526367600"; d="scan'208";a="68945479" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by FMSMGA003.fm.intel.com with ESMTP; 31 Jul 2018 08:09:19 -0700 Received: from irsmsx107.ger.corp.intel.com ([169.254.10.193]) by IRSMSX153.ger.corp.intel.com ([169.254.9.210]) with mapi id 14.03.0319.002; Tue, 31 Jul 2018 16:09:19 +0100 From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com> To: Thomas Monjalon <thomas@monjalon.net> CC: "dev@dpdk.org" <dev@dpdk.org>, "Shelton, Benjamin H" <benjamin.h.shelton@intel.com> Thread-Topic: [dpdk-dev] [PATCH] ethdev: Clarify usage of TM node parent update API function Thread-Index: AQHUGGNVoKmz272yhkCNSpHcQ5RAN6SpfmcAgAARlIA= Date: Tue, 31 Jul 2018 15:09:17 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E77C744@IRSMSX107.ger.corp.intel.com> References: <20180710153301.546-1-benjamin.h.shelton@intel.com> <1748890.xKDDESA46q@xps> In-Reply-To: <1748890.xKDDESA46q@xps> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] ethdev: Clarify usage of TM node parent update API function X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Tue, 31 Jul 2018 15:09:28 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas@monjalon.net] > Sent: Tuesday, July 31, 2018 4:06 PM > To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com> > Cc: dev@dpdk.org; Shelton, Benjamin H <benjamin.h.shelton@intel.com> > Subject: Re: [dpdk-dev] [PATCH] ethdev: Clarify usage of TM node parent > update API function >=20 > Cristian, review please? >=20 > 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 <benjamin.h.shelton@intel.com> > [...] > > /** > > * 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(= ) >=20 >=20 >=20 Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>