From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id C30CBA04B6; Sun, 11 Oct 2020 22:11:51 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3984F1D55E; Sun, 11 Oct 2020 22:11:49 +0200 (CEST) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 327291BACE for ; Sun, 11 Oct 2020 22:11:47 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 0E454D19; Sun, 11 Oct 2020 16:11:44 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Sun, 11 Oct 2020 16:11:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= Ui1wzfrtujPoJDyJmR7xU9/w5CMN6jqHe9uy3/A9hi8=; b=CnP5qRbd8JZyV4/m +mLPBWCU4tA9iiVAXY90MhvWJ1U19NbueX5fhoyXtEkcvLsGeglLrXeBJ9TOGBN0 2gC8FVQmUT0/x5bRq1Y8/HeeDBmYmECbx+AgnvYSrjsixhSP9g0934kQLyWD6T7e Am1n2QyNdQzEDJptOmCA39adNpxV86jA/EPDLQC6CcEUYfIaden1bJ940prLR2xn boHWjkLnVVaWQPCwL6FMqIa1x2rcFhJ+WXqH7S41V6nrUPSuJH54NPuS7IwBK1JP I626qCPIzMNZA4mfNSxSvghhgFi0D8pUQSyIHcL3Cs104BygqbzNUHkD2LtmdXv8 WGku8w== 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=Ui1wzfrtujPoJDyJmR7xU9/w5CMN6jqHe9uy3/A9h i8=; b=aWBwWGnZkEP0wsex2TbwEaCZvgppGwA9H+de9nlo6nL8uPbNISTcFsczo Tb0/19j2+aX8pDV541//qvTsKQlnw0a39LOgaqROcx7vHSwkx8Fn/7kI2aZG+FI1 MLNeYOZGK3E4eNWj+04PSz+wA7PdSqYdOX51luVnVFJ1g6Dr175T2FO3mR4KAcTH hcPMlS7HQ1+6hj5o+8QPihe2C7ItBkTdthr2pjzF01U0wjVM0WjZnEjUB4EHF8Ea PE5p0EteDae20iYa8ZYgCXzJwMu8uwAmsRHrW+KdPqMTDARxJZ5x2OthMIZEIRvm vkzDXkdyIAVRWk2woUst6eesHRmgQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrheehgddugeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id C6297306467E; Sun, 11 Oct 2020 16:11:43 -0400 (EDT) From: Thomas Monjalon To: Savinay Dharmappa Cc: cristian.dumitrescu@intel.com, jasvinder.singh@intel.com, dev@dpdk.org Date: Sun, 11 Oct 2020 22:11:42 +0200 Message-ID: <1771845.gd1I6FXUA8@thomas> In-Reply-To: <20201009123919.43004-1-savinay.dharmappa@intel.com> References: <20201007140915.19491-1-savinay.dharmappa@intel.com> <20201009123919.43004-1-savinay.dharmappa@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v9 0/8] Enable dynamic config of subport bandwidth 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 09/10/2020 14:39, Savinay Dharmappa: > DPDK sched library allows runtime configuration of the pipe profiles to the > pipes of the subport once scheduler hierarchy is constructed. However, to > change the subport level bandwidth, existing hierarchy needs to be > dismantled and whole process of building hierarchy under subport nodes > needs to be repeated which might result in router downtime. Furthermore, > due to lack of dynamic configuration of the subport bandwidth profile > configuration (shaper and Traffic class rates), the user application > is unable to dynamically re-distribute the excess-bandwidth of one subport > among other subports in the scheduler hierarchy. Therefore, it is also not > possible to adjust the subport bandwidth profile in sync with dynamic > changes in pipe profiles of subscribers who want to consume higher > bandwidth opportunistically. > > This patch series implements dynamic configuration of the subport bandwidth > profile to overcome the runtime situation when group of subscribers are not > using the allotted bandwidth and dynamic bandwidth re-distribution is > needed the without making any structural changes in the hierarchy. > > The implementation work includes refactoring the existing api and > data structures defined for port and subport level, new APIs for > adding subport level bandwidth profiles that can be used in runtime. > > --- > v8 -> v9 > - updated ABI section in release notes. > - Addressed review comments from patch 8 > of v8. I was asking a question in my reply to v8 but you didn't hit the "reply" button. One more question: why don't you keep the ack given by Cristian in v7?