DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kantecki, Tomasz" <tomasz.kantecki@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
	"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] eal: Initial implementation of PQoS EAL extension
Date: Mon, 22 Feb 2016 13:12:51 +0000	[thread overview]
Message-ID: <E79CF84CF47B0B42B66F4F5835125F9C817B2425@IRSMSX101.ger.corp.intel.com> (raw)

> 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?

Thanks for the feedback - we heard about dependency problem from a few sources.
 
> 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?

Thanks for the suggestion and the feedback.

Off the mail list, we received feedback that extending EAL commands is not an option due to Intel Architecture nature of CAT.
Consequently, we changed direction when working on V2 PQoS patches in roder to: 
- reduce DPDK PQoS code print and reuse existing open source code
- remove IA specific options from EAL

Current V2 patch, yet to be shared on the mail-list in a few days, implements a sample code (reuse of skeleton) that links against existing 01.org PQoS library. This eliminates need for code included in V1 librte_pqos patch.
The same sample code implements a C module that parses application specific part of the command line with CAT configuration options (same format as V1 EAL command). The module is easy to re-use in other applications as needed.
In the future, if there is a need to change this C module into a regular DPDK library then we'll be happy to do so.

Are you OK with concept behind V2 PQoS patch as described above?

Thanks,
Tomasz 
--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.

             reply	other threads:[~2016-02-22 13:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 13:12 Kantecki, Tomasz [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2016-02-24 15:14 Ananyev, Konstantin
2016-02-24 16:30 ` Thomas Monjalon
2016-01-29 13:29 Wojciech Andralojc
2016-02-16 16:36 ` 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=E79CF84CF47B0B42B66F4F5835125F9C817B2425@IRSMSX101.ger.corp.intel.com \
    --to=tomasz.kantecki@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).