From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) by dpdk.org (Postfix) with ESMTP id 3490FCFEC for ; Tue, 28 Mar 2017 15:30:32 +0200 (CEST) Received: by mail-lf0-f53.google.com with SMTP id x137so38143360lff.3 for ; Tue, 28 Mar 2017 06:30:32 -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:in-reply-to :references:mime-version:content-transfer-encoding; bh=exJlTWs5eSQmN2WlLCYHuM19F+B5BE0TJjBqu0Ukn9M=; b=chhJT+tbBUqxas63fNGNXge+QEQsEH/wpbRGtJnHxnKu0MgYBP3AOHU9Zy45D4TZGv o2pjL7Q8bABxbwYObGNCeJbVUwp1DuoDLl6eUWKpAJhEjb+m00XhwRLcQxBNdSDKyMQw Sj9jvFC5MJADEOjJZiDJvKuzvLvrO99e9U7nW6e6l3RREF+Cez5MV7Zfm09OPhj7uDRY 9Ai4xTVQiOIn5qVMknbcek9VLxhlbWa2N81U1XnN+pCxpkP/nCo5DlLyEjlmd9aVg4V4 8I5qF43CzejHN9JKda6CuJD6VDdbEU2Sye61BIRLWirlThl1xFcNEe8WwcAIMmfEH7xj 9Swg== 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 :in-reply-to:references:mime-version:content-transfer-encoding; bh=exJlTWs5eSQmN2WlLCYHuM19F+B5BE0TJjBqu0Ukn9M=; b=PSmMoo3bb3GCINz4JuvsHYUW2ZsBi7+JmYwsp8COT0ltV8XyEV+q/YVTNt9EMtg2rg iXtINmJby/V0qL+ogs++DEF2hIqjsYWGwfaYDnyUIFIxc31slBn2+Z7K7UMFYFNcwQIh yDek14WOkIaFXoa8kszMCko1iG9xijrEQZNjwUSySNYF6HaDl3OzAwVYmgtbNVQ2AnaF N4D5rcanMDZWCoNT3j2U9WJccunSsj7KbKv8k5V2evcjh/CWzRCIGptVXIH0DKc9GVUK eHpDR3flIGJiNARB6iQ8228nBrFizOof3iuYkFAQvAkV7U7U8ClVHgwx2fuxeIjZEVy8 81VQ== X-Gm-Message-State: AFeK/H0u8rVahtwvkDV8FysT9Far2kfQEG8ujhU4DcafDhSZs5zRvZA3IpjrhJmw/u66Kmsy X-Received: by 10.28.170.206 with SMTP id t197mr14961867wme.61.1490707831603; Tue, 28 Mar 2017 06:30:31 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id 100sm4904265wrb.33.2017.03.28.06.30.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Mar 2017 06:30:31 -0700 (PDT) From: Thomas Monjalon To: "Wiles, Keith" Cc: dev@dpdk.org, Olivier Matz , techboard@dpdk.org Date: Tue, 28 Mar 2017 15:30:30 +0200 Message-ID: <2035625.W01lfWd7dv@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: <1976507.q6Vb44MXhO@xps13> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Subject: Re: [dpdk-dev] [RFC] New CLI for DPDK 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 13:30:32 -0000 2017-03-28 13:19, Wiles, Keith: > > On Mar 28, 2017, at 5:06 AM, Thomas Monjalon wrote: > > 2017-03-24 14:48, Wiles, Keith: > >> True CLI is not the heart of DPDK, but adding a better supported C= LI could be a reasonable addition to DPDK for developers to create a re= al produce instead of cmdline, which is stated was not a CLI for a real= product. > >=20 > > We can ask to the techboard whether CLI is in DPDK scope. > > My position: it is neither in the scope of the repo nor in the scop= e of dpdk.org. >=20 > The goal is to replace the cmdline with CLI or at least provide a muc= h better supported and easier solution for DPDK developers. >=20 > The CLI was written just for DPDK and uses DPDK APIs only, so to me i= t is related to DPDK like any other tool or library we have in DPDK tha= t is not really providing packet transport. We have a number of these i= n DPDK today and having a library repo on DPDK.org is the very reasonab= le. >=20 > Also I thought we decided to add the repo to DPDK.org and the only re= ason we are revisiting if CLI should be on DPDK.org is how we support e= xternal libs of this type. >=20 > Thomas started out not liking the name of librte_cli and wanted some = other name. I suggested =E2=80=98cli=E2=80=99, but I wanted to keep the= librte_cli name as I wanted to be able to pull the librte_cli into the= DPDK/lib directory to make it simpler to integrate into DPDK for the d= eveloper. Building library or applications external to DPDK has a few i= ssues and not completely supported well in DPDK. >=20 > I would like to clone DPDK then clone librte_cli into the DPDK/lib di= rectory allowing librte_cli to be built as a internal library. Then add= the config option to the common_base and DPDK/lib/Makefile to allow th= e library to be built. This allow the developer to find the include and= library easily, which then allows us to start looking at updating the = current apps to use CLI. >=20 > I could provide a patch to DPDK to help integrate CLI into DPDK witho= ut modifying DPDK today for the developer to be able to use CLI as a st= andard internal library. My goal is to provide a cleaner solution for D= PDK developers and a DPDK support CLI. >=20 > I am now a bit confused as to why Thomas has objected here and reques= ted to be push to the TechBoard. I am sorry, I have realized in the discussion that it is not my call an= ymore to decide which repo can be added on dpdk.org. I have to apply a Technical Board decision which must comply with the (= upcoming) Governing Board directives.