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 B2C62A046B for ; Wed, 26 Jun 2019 23:33:55 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C1FF21E25; Wed, 26 Jun 2019 23:33:54 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 9E95D1E20 for ; Wed, 26 Jun 2019 23:33:53 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 392ED21F6D; Wed, 26 Jun 2019 17:33:53 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 26 Jun 2019 17:33:53 -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=mesmtp; bh=t5jIUkDrMXi5njJlLgM4kDqiW9OuXpP/3FKC2eM8xI4=; b=rwAbD0+n+cVu 6lbmxKAkUsjhcwgSg5iJwGAOr+vrLvj6wixHR72VBleTlReUWDUVJoSUoXoNGR8R Vy9yZm1lRGymP2cn/rqVXTxvpuJbX+fHlzpWoVUMNZj5lo96vHXlEKMaBEGbcXIw ZFQvjE0nBeeB14iZJJ2E7MdCsPGEFiY= 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=fm3; bh=t5jIUkDrMXi5njJlLgM4kDqiW9OuXpP/3FKC2eM8x I4=; b=uXQ+kSbbQVTh/X6busYVWIadPSzxFuddaeyNlKXLuPSVQKYRXDKhsqb6b YUCYs0BhRwAE4hbmbHKgFFubk1erON6Hn6LU2RVcXBPg142Otaesumm32Nc9KOmu zL7ndUZiJrp+UbNYnyX/24UOJfysm5QGBTf01bHqe9EJ4EEBR1lYNiUSB8ecan32 S2K4S6s2XBfU4QRlB/eiTh+SNnIn2Bgg8vsyMMpjr4aoL+eH3f8pDvyW8mBwQJAw iLZjkIgy6WjObLp9ZSLb8Jrd0dGwvFWFNafr2u7oErl4AwgIfVnKdZJwd2KfoTh+ LCmipK/NjnR/jgijWQQ3jMVhPMn6g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudeigdduieekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedu 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 5C975380074; Wed, 26 Jun 2019 17:33:52 -0400 (EDT) From: Thomas Monjalon To: Jasvinder Singh Cc: dev@dpdk.org, cristian.dumitrescu@intel.com Date: Wed, 26 Jun 2019 23:33:51 +0200 Message-ID: <5022647.LnWanB60ff@xps> In-Reply-To: <20190625153217.24301-1-jasvinder.singh@intel.com> References: <20190528120553.2992-2-lukaszx.krakowiak@intel.com> <20190625153217.24301-1-jasvinder.singh@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 00/28] sched: feature enhancements 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" 25/06/2019 17:31, Jasvinder Singh: > Jasvinder Singh (27): > sched: update macros for flexible config > sched: update subport and pipe data structures > sched: update internal data structures > sched: update port config API > sched: update port free API > sched: update subport config API > sched: update pipe profile add API > sched: update pipe config API > sched: update pkt read and write API > sched: update subport and tc queue stats > sched: update port memory footprint API > sched: update packet enqueue API > sched: update grinder pipe and tc cache > sched: update grinder next pipe and tc functions > sched: update pipe and tc queues prefetch > sched: update grinder wrr compute function > sched: modify credits update function > sched: update mbuf prefetch function > sched: update grinder schedule function > sched: update grinder handle function > sched: update packet dequeue API > sched: update sched queue stats API > test/sched: update unit test > net/softnic: update softnic tm function > examples/qos_sched: update qos sched sample app > examples/ip_pipeline: update ip pipeline sample app > sched: code cleanup I feel the titles of type "update some API" might be more meaningful if giving the intent (flexibility) or more context (what is updated). Not sure because I don't know this library enough.