From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id BDDFC1D310 for ; Fri, 6 Apr 2018 18:51:52 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 3152D20D1F; Fri, 6 Apr 2018 12:51:52 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 06 Apr 2018 12:51:52 -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=AzCZV7OuKItTm6Aac5kt45E03s DpYZhzCv1wOCsJ9S0=; b=B8KmVM4hXa+F9wZnUhvEbeYcoOUTqX1uDmiZ+VmOul TgXBcZZOCq2Trej98Mbv+4Dvy4QKThRZR7veG82bzk0vfzldDCR47WSH3lzpK+ky mV/YEAqsDsdPT0VRV1V2GgT+8IiaqUN5atF3tZnDfgVHJmD7SRTpNIAtj1MYMEIQ 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=AzCZV7 OuKItTm6Aac5kt45E03sDpYZhzCv1wOCsJ9S0=; b=TgtX1aXA21Lq9N/VV0uUcC jrlN1eAOhQjfxKtWh2vTU97iOWO81oH+2RqAhP1Xyn53fKi7u7HyN19TXToAsJbA GsRB36OGjWFvfod9UkdbHNNHUclMAh+hugLBmRtz4Ub1Edo8GEnR+vocxYceLXn2 3742aKSU2zETRsL9VSV2lTW6mopoGhQLlVCur5ZTgdKBB6MsZKuw5p0+kIVJ5mZP GKYRZh6zw9s+KkbaaH5Hhh2P71peVC9AA4DzAZI45CgVeFPAhONOy/aeQZ3KDZ6U jQbbLzjCUvt8B84lgj1zznrXueEwcB8d0x3QxY6VLNvoSeqMEs3ZkArGeQvcRHVQ == 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 92BE1E43C8; Fri, 6 Apr 2018 12:51:51 -0400 (EDT) From: Thomas Monjalon To: "Singh, Jasvinder" Cc: dev@dpdk.org, "Dumitrescu, Cristian" Date: Fri, 06 Apr 2018 18:51:51 +0200 Message-ID: <1695939.d5zgjGaqM5@xps> In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891267BB3B5F8@IRSMSX108.ger.corp.intel.com> References: <20180405114959.96952-1-jasvinder.singh@intel.com> <3EB4FA525960D640B5BDFFD6A3D891267BB3B5F8@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: add meter API change to release notes 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: Fri, 06 Apr 2018 16:51:53 -0000 05/04/2018 14:03, Dumitrescu, Cristian: > From: Singh, Jasvinder > > > > Update the release notes with meter api change to support configuration > > profiles. > > > > Signed-off-by: Jasvinder Singh > > --- > > --- a/doc/guides/rel_notes/release_18_05.rst > > +++ b/doc/guides/rel_notes/release_18_05.rst > > @@ -72,6 +72,16 @@ API Changes > > Also, make sure to start the actual text at the margin. > > ========================================================= > > > > +* **Meter API updated to accomodate configuration profiles.** > > + > > + The meter API is changed to support meter configuration profiles. The > > + configuration profile represents the set of configuration parameters > > + for a given meter object, such as the rates and sizes for the token > > + buckets. These configuration parameters were previously the part of > > meter > > + object internal data strcuture. The separation of the configuration > > + parameters from meter object data structure results in reducing its > > + memory footprint which helps in better cache utilization when large > > number > > + of meter objects are used. > > Acked-by: Cristian Dumitrescu Applied with a small formatting change: * meter: updated to accommodate configuration profiles.