From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [RFC] ethdev: abstraction layer for QoS hierarchical
	scheduler
Date: Tue, 06 Dec 2016 23:14:13 +0100
Message-ID: <2204708.uGZ3ieR731@xps13>
References: <1480529810-95280-1-git-send-email-cristian.dumitrescu@intel.com>
 <20161206115124.67ccc0c7@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org, Cristian Dumitrescu <cristian.dumitrescu@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wj0-f180.google.com (mail-wj0-f180.google.com
 [209.85.210.180]) by dpdk.org (Postfix) with ESMTP id E87B7106A
 for <dev@dpdk.org>; Tue,  6 Dec 2016 23:14:15 +0100 (CET)
Received: by mail-wj0-f180.google.com with SMTP id xy5so339561662wjc.0
 for <dev@dpdk.org>; Tue, 06 Dec 2016 14:14:15 -0800 (PST)
In-Reply-To: <20161206115124.67ccc0c7@xeon-e3>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2016-12-06 11:51, Stephen Hemminger:
> Rather than reinventing wheel which seems to be DPDK Standard
> Procedure, could an existing abstraction be used?

Stephen, you know that the DPDK standard procedure is to consider
reviews and good comments ;)