From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C4179A0508; Thu, 14 Apr 2022 11:53:43 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 61AC140041; Thu, 14 Apr 2022 11:53:43 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 83D034003F for ; Thu, 14 Apr 2022 11:53:41 +0200 (CEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 2A4635C022D; Thu, 14 Apr 2022 05:53:41 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 14 Apr 2022 05:53:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; t=1649930021; x= 1650016421; bh=Ne1NF3DAfDv5yirnJo9gUrEtct9QHvgjc1XxTdWsyus=; b=U vJt20IEVa31f+gok1SlJT2bsngIN3crg9ycJ0kpBIENblE4aXAlQ0K0T0L4TnLt1 BRu9XoDVAZ8HRDrgcVzlVH07TarTsaQK8JzyhhtxNZj9LAJrXxJ11FPvr7UyDxl4 XkB2BomyOTRQH6n/LxYZIjg1dElY33P9+EtXcu8bOxRKQhNQ8yHEh67ohxWfVDKQ 9I+cVjEfyW/dUNynlqRL0KS9jLr4UQMghoB/TuEokYpeOGFJ5MVbLsJysU8lUSrp MGJQPJVmnmb2jPP3OCuozWbd/JepbzjlZfbnYXrEMbYOsmg/1rGvBCWRMmpYhT5H a2tARCmmuPy5Qndhn8EBQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1649930021; x=1650016421; bh=Ne1NF3DAfDv5y irnJo9gUrEtct9QHvgjc1XxTdWsyus=; b=siVV3vpXStGBQUN9uRaJ+dz09GZO9 3ck38iv/fh6ceN5GZ7pUcgpY90fFfsl52oggl66IzobFKc06d5uBb4hWvsltaI6X MOHCOuXw7NBkhi323RKmEIOvq8LQ2XgggDeDEkEs2gEozx7ThCIoFOYwcKgRv5Nv PHJNfr2i3Lp/zZNzb3TD5Ig1xowlJle/HeClpg+DasOlibfSFl4tNeWaTu/2jWJn LIkCvAfsEkRklKK9EV82dxN6KLIrU0npubOoZnDOJe3/oKkBKsbdhtruREpm8tSV vYtmbDb8S60DDH9aJrR8/JEJP5iuQfjPW/XjXpZELQPlirbU1ysgtJLjA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudelfedgvddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 14 Apr 2022 05:53:40 -0400 (EDT) From: Thomas Monjalon To: Marcin Danilewicz Cc: dev@dpdk.org, jasvinder.singh@intel.com, cristian.dumitrescu@intel.com, stephen@networkplumber.org Subject: Re: [dpdk][PATCH 2/2] sched: fix to manage TC OV at runtime Date: Thu, 14 Apr 2022 11:53:39 +0200 Message-ID: <5811274.31tnzDBltd@thomas> In-Reply-To: <20220407145153.238969-2-marcinx.danilewicz@intel.com> References: <20220407145153.238969-1-marcinx.danilewicz@intel.com> <20220407145153.238969-2-marcinx.danilewicz@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 07/04/2022 16:51, Marcin Danilewicz: > Added changes after review and increased throughput. > > Signed-off-by: Marcin Danilewicz I think these changes should be squashed with the first patch. You need to version your patches also: this one should have been v2, next one should be v3. And while at it, the best is to provide a changelog to make clear what was improved compared to last version. Please do not forget to Cc maintainers of sched. Probably they can help you to get the right formatting.