From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Wojciech Andralojc <wojciechx.andralojc@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: Initial implementation of PQoS EAL extension
Date: Tue, 16 Feb 2016 17:36:39 +0100 [thread overview]
Message-ID: <6407659.igNN1mJeGf@xps13> (raw)
In-Reply-To: <1454074193-133635-1-git-send-email-wojciechx.andralojc@intel.com>
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?
next prev parent reply other threads:[~2016-02-16 16:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 13:29 Wojciech Andralojc
2016-02-16 16:36 ` Thomas Monjalon [this message]
2016-02-22 13:12 Kantecki, Tomasz
2016-02-22 13:22 ` Thomas Monjalon
2016-02-23 10:03 ` Kantecki, Tomasz
2016-02-23 16:41 ` Thomas Monjalon
2016-02-23 23:03 ` Kantecki, Tomasz
2016-02-24 8:24 ` Thomas Monjalon
2016-02-24 10:10 ` Bruce Richardson
2016-02-24 10:22 ` Ananyev, Konstantin
2016-02-24 10:34 ` Thomas Monjalon
2016-02-24 11:21 ` Ananyev, Konstantin
2016-02-24 11:45 ` Thomas Monjalon
2016-02-24 13:47 ` Ananyev, Konstantin
2016-02-24 10:31 ` Thomas Monjalon
2016-02-24 11:00 ` Bruce Richardson
2016-02-24 15:14 Ananyev, Konstantin
2016-02-24 16:30 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6407659.igNN1mJeGf@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=wojciechx.andralojc@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).