From: "Liang, Cunming" <cunming.liang@intel.com>
To: dev@dpdk.org
Cc: "keith.wiles@intel.com; Chen Jing D(Mark)"
<jing.d.chen@intel.com>,
gerald.rogers@intel.com
Subject: Re: [dpdk-dev] [RFC 1/2] doc: introduction to prgdev
Date: Wed, 8 Feb 2017 11:30:02 +0800 [thread overview]
Message-ID: <65b7c8b3-0638-5f8e-ad8f-3a4c5eaaa096@intel.com> (raw)
In-Reply-To: <1484882498-18653-2-git-send-email-jing.d.chen@intel.com>
On 1/20/2017 11:21 AM, Chen Jing D(Mark) wrote:
> This is the documentation to describe what prgdev is, how to use
> prgdev API and accomplish an image download.
>
> Signed-off-by: Chen Jing D(Mark) <jing.d.chen@intel.com>
> ---
> doc/guides/prog_guide/prgdev_lib.rst | 457 ++++++++++++++++++++++++++++++++++
> 1 files changed, 457 insertions(+), 0 deletions(-)
> create mode 100644 doc/guides/prog_guide/prgdev_lib.rst
>
> diff --git a/doc/guides/prog_guide/prgdev_lib.rst b/doc/guides/prog_guide/prgdev_lib.rst
> new file mode 100644
> index 0000000..3917c18
> --- /dev/null
> +++ b/doc/guides/prog_guide/prgdev_lib.rst
> @@ -0,0 +1,457 @@
> +Overview
> +========
> +
[...]
> +When the set of APIs is introduced, a general question is why we need it in
> +DPDK community? Why we can't use offline tool to perform same thing? The answer
> +is the prgdev provide a generic, online API to applications, in the meanwile,
> +offers a capability to switch driver dynamically when downloaded image changed
> +personality and a new driver is required. Comparing offline tool, it have online
> +programmability (see below examples); Comparing online tool, it provides a
> +generic API for many HWs; Comparing generic online tool/API for many products,
> +it provides a capability to switch driver dynamically.
> +
> +There are various means to reach same goal, we'll try to find the best/better
> +way to approach. All above advantages will help prgdev to be a 'better choice'.
> +
>
One more notes.
DPDK takes over the devices in user space. The legacy tools usually
download the personality by kernel driver. They runs out of DPDK
context. When a DPDK process is running on top of the device, operation
to the device by the solo tool during the time causes resource conflict.
It's one of the motivations to have the native API allowing programming
the personality within DPDK context. Otherwise, it has to exit the
process if any personality change is required. Manually detaching the
device before using the solo tool may ease the conflict. However it
still limits the situation if the device allows multiple programmable
instances(e.g. AFUs in FPGA) which are working independently and
shouldn't be impact by each other.
[...]
next prev parent reply other threads:[~2017-02-08 3:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 3:21 [dpdk-dev] [RFC 0/2] Prgdev API Chen Jing D(Mark)
2017-01-20 3:21 ` [dpdk-dev] [RFC 1/2] doc: introduction to prgdev Chen Jing D(Mark)
2017-02-01 11:41 ` Jan Blunck
2017-02-03 9:21 ` Liang, Cunming
2017-02-06 9:16 ` Chen, Jing D
2017-02-08 3:30 ` Liang, Cunming [this message]
2017-01-20 3:21 ` [dpdk-dev] [RFC 2/2] prgdev: introduce generic prgdev API Chen Jing D(Mark)
2017-02-08 22:49 ` Stephen Hemminger
2017-02-08 23:06 ` Wiles, Keith
2017-02-09 2:23 ` Chen, Jing D
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=65b7c8b3-0638-5f8e-ad8f-3a4c5eaaa096@intel.com \
--to=cunming.liang@intel.com \
--cc=dev@dpdk.org \
--cc=gerald.rogers@intel.com \
--cc=jing.d.chen@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).