From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] eal: Initial implementation of PQoS EAL extension Date: Tue, 16 Feb 2016 17:36:39 +0100 Message-ID: <6407659.igNN1mJeGf@xps13> References: <1454074193-133635-1-git-send-email-wojciechx.andralojc@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Wojciech Andralojc Return-path: Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by dpdk.org (Postfix) with ESMTP id ECA1EC166 for ; Tue, 16 Feb 2016 17:38:11 +0100 (CET) Received: by mail-wm0-f49.google.com with SMTP id g62so116987164wme.1 for ; Tue, 16 Feb 2016 08:38:11 -0800 (PST) In-Reply-To: <1454074193-133635-1-git-send-email-wojciechx.andralojc@intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-01-29 13:29, Wojciech Andralojc: > EAL extension allows CAT and CDP technologies to be > configured via "--l3ca*" parameters. EAL should not depend on the PQoS library. Please could you hook the command line parsing and help to add these new options from outside? > Reworking existing applications to make use of DPDK PQoS library is > a heavy lift. This EAL extension is to make it easier by adding > new command line options. These new options allow to leverage CAT and > CDP technologies with existing code base without any additional > development effort. The command line options may be convenient in some cases but not straightforward for some applications. >>From now, the runtime options must be also configurable with an API. Please consider a clean configuration API first in the library. Then it can be hooked in the EAL command line. A thought: should we move the EAL command line in a separate library with a hook API?