From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f173.google.com (mail-wr0-f173.google.com [209.85.128.173]) by dpdk.org (Postfix) with ESMTP id 8B612CFBA for ; Tue, 28 Mar 2017 10:44:22 +0200 (CEST) Received: by mail-wr0-f173.google.com with SMTP id w43so79829712wrb.0 for ; Tue, 28 Mar 2017 01:44:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:mime-version :content-transfer-encoding; bh=SNc2rZuXEGgZPCaRUR6EKxQ1OTk7gn6lajRt35yecVY=; b=prqZdG/QQXMCkTnmHndV5f7GkFpVmilDi0Y7rxy+M5W0dqf+f3dtMsfrT/NRwxiUQP fzz1tXYReacNg9vgeboBWK4ref9qMci4p07qQnJmDIXye4UR9cKeTfDSQy+AE0CxegzY +ZJK6EhcucluzeHXLUDF2gm8I2KEGLbbupm2x4b44O2PP3OBKPL85ssbtahw3Ue38vDT /t56FyzvIglvq/AUdAcfUIPsIbz9BVas82BUam1jxNnWHNAioQtV0wfTOoE/gYYFD88v NaPj3i/Kw/7ASlxnlnnpDaFRXkkvf6DyHWr47FKvS5z1181xhSUmT4BzYtgLpfVVZPBC 6zLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :mime-version:content-transfer-encoding; bh=SNc2rZuXEGgZPCaRUR6EKxQ1OTk7gn6lajRt35yecVY=; b=fLfpCj3FdsFsFKilPb/7wMXjQaQugRoDQf+fHkpT5DPIXEA1jq5zsKEOR2omZlSMt0 Eo2PnU6rU3Ck10SFa0Ye73DLdSpEKAmiDLv/zmW05+MULOI34tdl168bVfEILkH6jVqs cxmGGxluW9S0C6Z1Pnu01R2omjHYhGQn8pqNMRds+QWnzY/GoDv2mqI3BHZ/OpyKt3mI rMxGF7flT2jTOEQcFMV4EdgubaZaQJJ9LMnNclijjJ13SEVwVgWO5zell86rBSpfYDkt MFHVsZFbP0L2IeD4ojj9/tDY/3pDYSpy0PmUbvqyLqXWak1NljJz/7GPFE9OKmon5OQY BsSA== X-Gm-Message-State: AFeK/H1s+eJrYeKneSktTvmqpmu7eRqJTCvtIwKyIq7HU1GCo+7snbn+T7P5Olc25e9vTAUO X-Received: by 10.28.195.214 with SMTP id t205mr12527623wmf.104.1490690662312; Tue, 28 Mar 2017 01:44:22 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id m83sm1144120wmc.7.2017.03.28.01.44.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Mar 2017 01:44:21 -0700 (PDT) From: Thomas Monjalon To: dev@dpdk.org Cc: cristian.dumitrescu@intel.com, hemant.agrawal@nxp.com, jerin.jacob@caviumnetworks.com Date: Tue, 28 Mar 2017 10:44:20 +0200 Message-ID: <2544195.RoHNEuVALo@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [dpdk-dev] new QoS/TM API and tree 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: Tue, 28 Mar 2017 08:44:22 -0000 At the last techboard meeting, it has been accepted to create a new git tree for the ongoing QoS work. (see minutes http://dpdk.org/ml/archives/dev/2017-March/061009.html) Quoting http://dpdk.org/ml/archives/dev/2017-March/060387.html " Can you please create a next-tree for QoS Traffic Management with the following details: Maintainer: Cristian Committers: Hemant, Jerin, Cristian " The last detail to discuss is the name of this tree. As it is probably going to be an important amount of work, this tree can live indefinitely as a next- tree to be pulled before each RC1. The suggested names were dpdk-next-qos and dpdk-next-tm. The question is equivalent to choose a name for the new API. Should it be rte_qos or rte_tm? Please let's think how it can evolve in future versions.