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 5BD6EA04DB; Thu, 15 Oct 2020 02:17:45 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BBEA71DA93; Thu, 15 Oct 2020 02:17:43 +0200 (CEST) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 902271D57B for ; Thu, 15 Oct 2020 02:17:42 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 55C62CDC; Wed, 14 Oct 2020 20:17:38 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 14 Oct 2020 20:17:38 -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= D2VoBG+9pJpJ1WqW8ThRyxXQTAnkRDFL9h/sfEwB+ew=; b=LRa4t9Qw3gz5OTkr DCBzveNkfSWl1UKTiZ6ArGDrtAeAkc4rDlqnVIa9SvqxDIBFeN5e29v7lORazWQg UP5esCpQH0VwFdQeDW7nw7Z/iNudE0mZnguHYqRlCo4YKc3rsZCAYkm0CwwXA3bJ 14uMAX39eyAvyWPhI9E2dCJL8C8LHyIj/RjWl5eXLsLU/58raUiBJ16PVQPACJGP A6ijFjSL8ZpMs03fF0g7Zp/+q8KCM+AEtLfUm/balZUy7ZjvfGZpz7stVNgONrKD LD0Hm2cs8Gz25aiRC5gSfQlic+Ma54VrVwVsn5AFNIR8gXAk/pkxNTRTJd9WoNId E/OWdA== 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=D2VoBG+9pJpJ1WqW8ThRyxXQTAnkRDFL9h/sfEwB+ ew=; b=nHe7qFzQ9OSUehCdcQJDj5vrAgJMrefxsExgEh731Dn/V3ApmB4xiE4HL e1TbLgp1zWQNpvBpcCfxfFBsSZmzs/Ey1cJoXdAVfoH9cN2+OZHlEbD1HYRXX+yd iHvXWH3/f4l/6QtJU2an0OAIw/ReJLN77YmuzGVAnQqmUq8M5oUqK28jeJgwlmJq Z8u1ti8ZVQfZQCZUZYMaTp0fTwPbYOwgwjMep00m/9Ctp4MtpuxlNQEb6W4ZRmFi 8zV5zVhP9m0F4udqj/Pn5Aj9aXXI+hSz1l0hdwyD7kr9Way2u2pDQL3ZB0sDI8yv HMZrzVKmd5ij+WT5UQ/IIaxFTg/1g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedriedvgdefvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei iedvffegheenucfkphepjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvth 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 005B0306467D; Wed, 14 Oct 2020 20:17:36 -0400 (EDT) From: Thomas Monjalon To: Savinay Dharmappa Cc: cristian.dumitrescu@intel.com, jasvinder.singh@intel.com, dev@dpdk.org Date: Thu, 15 Oct 2020 02:17:36 +0200 Message-ID: <2152489.h1XRFohYtY@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. > > Savinay Dharmappa (8): > sched: add support profile table > sched: introduce subport profile add function > sched: update subport rate dynamically > example/qos_sched: update subport rate dynamically > example/ip_pipeline: update subport rate dynamically > drivers/softnic: update subport rate dynamically > app/test_sched: update subport rate dynamically > sched: remove redundant code > > Series-acked-by: Cristian Dumitrescu Applied with few minor changes in release notes, thanks