From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 3C30AFFA for ; Fri, 3 Feb 2017 10:21:15 +0100 (CET) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga101.fm.intel.com with ESMTP; 03 Feb 2017 01:21:14 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,328,1477983600"; d="scan'208,217";a="60417609" Received: from shwdeisgchi017.ccr.corp.intel.com (HELO [10.239.66.156]) ([10.239.66.156]) by orsmga005.jf.intel.com with ESMTP; 03 Feb 2017 01:21:12 -0800 To: Jan Blunck , "Chen Jing D(Mark)" References: <1484882498-18653-1-git-send-email-jing.d.chen@intel.com> <1484882498-18653-2-git-send-email-jing.d.chen@intel.com> Cc: dev@dpdk.org, keith.wiles@intel.com, gerald.rogers@intel.com From: "Liang, Cunming" Message-ID: Date: Fri, 3 Feb 2017 17:21:10 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [RFC 1/2] doc: introduction to prgdev X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2017 09:21:17 -0000 Hi, On 2/1/2017 7:41 PM, Jan Blunck wrote: > On Fri, Jan 20, 2017 at 4: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) >> --- >> 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 > [...]