From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 3DE04DED for ; Mon, 23 Apr 2018 21:47:24 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 930552148A; Mon, 23 Apr 2018 15:47:23 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 23 Apr 2018 15:47:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=bIRXl3LncJ2+V2NLj/SHp/2DfW CxDBEeKmkClnr1lQ4=; b=hL1YdcneZIkGCrBZagOZXpZbvxdQlY16E26ND6nlFa wI8RLOKCg+aRQ5cxdOpIhk89X3F+Ot0Gfg8SPcg/VlMZjYUiDrPksKQZmoFfFfKn 3TmWMx+LHbTJ/T2WDN5UPDKio3P2+b3Ppv5VZ8hkYcH+QIYHluwc2zVqaEXR1Zf7 o= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=bIRXl3 LncJ2+V2NLj/SHp/2DfWCxDBEeKmkClnr1lQ4=; b=bg8gB4FYupXnBhOUd2F74k kda3MUwin1VLbFV/C9il5snV//Wyhq+SiZ+v6HtWToJSBqfacq70qj/faW4YQjWf YF2mlYbxkUFA6aiSg6OnhBTY/4b37fIMRuCsm3OUpLUeqRwiPCgJzB4Cp5kNDYMP JTalt6arfPxQodTqqE9LU1nDuXNGsUMC604bxc6RDb1EWGTWr6Mm+qPiWAYvniih 2gFbOFCuIp1mh4dD6o4PWYVsQnCM/jecd5Z6eCMVcUA5B3ByVk/e2KMHyW1XeQ3w yJwmhoSzL1nJfeR+JRrfikV6Mw/T7XbPIyURzNVNikus9vKrqvU4MP1Z1ls+f/4Q == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B587DE43E8; Mon, 23 Apr 2018 15:47:22 -0400 (EDT) From: Thomas Monjalon To: Tomasz Duszynski Cc: dev@dpdk.org, "Singh, Jasvinder" , "Lu, Wenzhuo" , "Wu, Jingjing" Date: Mon, 23 Apr 2018 21:47:21 +0200 Message-ID: <7191843.31ITM4uCTE@xps> In-Reply-To: <54CBAA185211B4429112C315DA58FF6D332FA7C3@IRSMSX103.ger.corp.intel.com> References: <1517297828-3111-1-git-send-email-tdu@semihalf.com> <20180216081339.GB25327@sh> <54CBAA185211B4429112C315DA58FF6D332FA7C3@IRSMSX103.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] app/testpmd: allow setting shaper profile id to none X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Apr 2018 19:47:24 -0000 16/02/2018 10:38, Singh, Jasvinder: > > On Tue, Jan 30, 2018 at 08:37:08AM +0100, Tomasz Duszynski wrote: > > > Private shaper profiles are attached to nodes defined in traffic > > > manager hierarchy. > > > > > > Since not every node must have a configured shaper testpmd should > > > allow setting shaper profile id to invalid > > > (RTE_TM_SHAPER_PROFILE_ID_NONE) easily. > > > > > > This patch follows same approach as in case of setting parent id of > > > the root node i.e passing a negative value sets node id to > > > RTE_TM_NODE_ID_NULL. > > > > > > In case of private shaper profile negative value will set shaper > > > profile id to RTE_TM_SHAPER_PROFILE_ID_NONE. > > > > > > Signed-off-by: Tomasz Duszynski > > Reviewed-by: Jasvinder Singh Applied, thanks