From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by dpdk.org (Postfix) with ESMTP id 0CAC37E74 for ; Fri, 17 Oct 2014 20:42:28 +0200 (CEST) Received: by mail-wi0-f173.google.com with SMTP id fb4so2828819wid.12 for ; Fri, 17 Oct 2014 11:50:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=QjzSKZjH9QDJub+3NgBtXd9tbAIS1HZ/0DDIHsmtiho=; b=CcTyX29Rj2i4B83H5vhhdfv3rXQXttWe3t9/QaziVi0f6Q49HlcG7cYEp2MRgtfQ1B S244u6yHJckbrDMvFLsx3mpplTDnfujilh21MSN/MQ+fjKbR43paAB2YXKFkryWqXzUZ PNjoaSFCkdZAzAyH56+RwedHSAbWo/yn19dytVvcOOeT696VAoNseVdbCduNIcwc0xQW hSbr5sgsHhV9iUcUfFcbh+d1YTOWfojOatJJRPpJOBHpWkhy7MkuRacD8D/4gdZQVFGG 4BDK6QMB3PMsZHS4T0hrMNY/Cf1WtiMfwljs9GCSglYlD68HGroQNhZvrUJyFLLR0RKJ 9mmw== X-Gm-Message-State: ALoCoQnKFjmIVIAqNmaYPJD+MilEdsKU9XtSkQ1uaNX9mCo3YA9hJYG8EGMFwLhVmfbBS+Xj/8g9 X-Received: by 10.194.243.131 with SMTP id wy3mr5799986wjc.129.1413571827057; Fri, 17 Oct 2014 11:50:27 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id o1sm2626876wja.25.2014.10.17.11.50.25 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Oct 2014 11:50:26 -0700 (PDT) From: Thomas Monjalon To: "Dumitrescu, Cristian" Date: Fri, 17 Oct 2014 20:50:10 +0200 Message-ID: <3206025.nBbheCu3gE@xps13> Organization: 6WIND User-Agent: KMail/4.14.1 (Linux/3.16.4-1-ARCH; KDE/4.14.1; x86_64; ; ) In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891262E090572@IRSMSX108.ger.corp.intel.com> References: <1401905319-8882-1-git-send-email-cristian.dumitrescu@intel.com> <10629744.mhUtJ8hJ7T@xps13> <3EB4FA525960D640B5BDFFD6A3D891262E090572@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [v2 20/23] librte_cfgfile: interpret config files X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2014 18:42:28 -0000 2014-10-17 18:16, Dumitrescu, Cristian: > Hi Tomas, > > Yes, you're right, we need to close on this pending item. > Thanks for bringing it up. > > I am currently working on a patch series, once I send it out > I will come back and look into to qos_sched. Is this OK with you? Yes, thank you. > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Thursday, October 16, 2014 5:46 PM > To: Dumitrescu, Cristian > Cc: dev@dpdk.org; Wu, Jingjing; Liu, Jijiang > Subject: Re: [dpdk-dev] [v2 20/23] librte_cfgfile: interpret config files > > Hi Cristian, > > 2014-06-04 19:08, Cristian Dumitrescu: > > This library provides a tool to interpret config files that have standard > > structure. > > > > It is used by the Packet Framework examples/ip_pipeline sample application. > > > > It originates from examples/qos_sched sample application and now it makes > > this code available as a library for other sample applications to use. > > The code duplication with qos_sched sample app to be addressed later. > > 4 months ago, you said that this duplication will be adressed later. > Neither you nor anyone at Intel submitted a patch to clean up that. > I just want to be sure that "later" doesn't mean "never" because > I'm accepting another "later" word for cleaning old filtering API. > > Maybe you just forgot it so please prove me that I'm right to accept > "later" clean-up, in general. > > Thanks