From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Kantecki, Tomasz" <tomasz.kantecki@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] eal: Initial implementation of PQoS EAL extension
Date: Tue, 23 Feb 2016 17:41:07 +0100 [thread overview]
Message-ID: <91026831.UvMIbM9v17@xps13> (raw)
In-Reply-To: <E79CF84CF47B0B42B66F4F5835125F9C817B2C56@IRSMSX101.ger.corp.intel.com>
2016-02-23 10:03, Kantecki, Tomasz:
> > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > > Are you OK with concept behind V2 PQoS patch as described above?
> >
> > So you mean that PQoS don't really need some DPDK integration?
> > You just want to show how to use it with DPDK?
>
> You are correct. The technology can be used without tight DPDK integration but will require users to reach out to existing open source code.
> Based on received feedback about EAL PQoS extensions we backed off to sort of a sample code.
If there is nothing specific in DPDK for PQos, why writing an example in DPDK?
Maybe the example should be better in the library itself.
I suggest to mention the library in doc/guides/linux_gsg/nic_perf_intel_platform.rst
next prev parent reply other threads:[~2016-02-23 16:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 13:12 [PATCH] eal: Initial implementation of PQoS EAL extension Kantecki, Tomasz
2016-02-22 13:22 ` Thomas Monjalon
2016-02-23 10:03 ` Kantecki, Tomasz
2016-02-23 16:41 ` Thomas Monjalon [this message]
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=91026831.UvMIbM9v17@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=tomasz.kantecki@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.