From: "Liang, Cunming" <cunming.liang@intel.com>
To: Jan Blunck <jblunck@infradead.org>,
"Chen Jing D(Mark)" <jing.d.chen@intel.com>
Cc: dev@dpdk.org, keith.wiles@intel.com, gerald.rogers@intel.com
Subject: Re: [dpdk-dev] [RFC 1/2] doc: introduction to prgdev
Date: Fri, 3 Feb 2017 17:21:10 +0800 [thread overview]
Message-ID: <a236361a-7ba4-6384-f9b8-cf0b726460cb@intel.com> (raw)
In-Reply-To: <CALe+Z01mw0pWNsKNZikReM7RAoW1rDuUzykYZWzT2zw178V1zg@mail.gmail.com>
Hi,
On 2/1/2017 7:41 PM, Jan Blunck wrote:
> On Fri, Jan 20, 2017 at 4:21 AM, Chen Jing D(Mark)
> <jing.d.chen@intel.com> 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
[...]
> From my point of view this doesn't belong into the DPDK. On Linux this
> is traditionally handled by udev and you already have the freedom to
> use userspace applications to program a device requiring firmware in
> that case. I don't believe that modeling this in the DPDK explicitly
> is the right thing to do.
Good point, but not sure udev has user space device driver support or not.
>
> Especially if the device supports changing personality it is required
> to unplug the existing personality before reprogramming. You can do
> this already today. Also writing OOB firmware data that changes
> configuration should be possible today by handling interrupts.
It's going to allow changing personality in DPDK user space runtime.
If the personality is not belong to a device but part of the component,
unplug isn't helpful too much.
>
> Maybe we can come up with an example application that demonstrates how
> the different infrastructure components could get orchestrated. Do you
> have a device in mind that supports this?
The coming Purley platform has SKU for Xeon-FPGA.
The FPGA connecting with Xeon has dedicated pcie device id.
The AFU personality for packet I/O depends on the RTL image.
Changing the personality in runtime could be one of the situation.
Regards,
Cunming
>
> Regards,
> Jan
>
[...]
next prev parent reply other threads:[~2017-02-03 9:21 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 [this message]
2017-02-06 9:16 ` Chen, Jing D
2017-02-08 3:30 ` Liang, Cunming
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=a236361a-7ba4-6384-f9b8-cf0b726460cb@intel.com \
--to=cunming.liang@intel.com \
--cc=dev@dpdk.org \
--cc=gerald.rogers@intel.com \
--cc=jblunck@infradead.org \
--cc=jing.d.chen@intel.com \
--cc=keith.wiles@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).