From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Yuan Kevin <kevin-yuan@live.com>, "users@dpdk.org" <users@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-users] How DPDK initialize PCIe DMA engine?
Date: Mon, 2 Sep 2019 09:31:38 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA6758D967E@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <BYAPR08MB4086BDED2444287871276876F2BF0@BYAPR08MB4086.namprd08.prod.outlook.com>
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Yuan Kevin
> Sent: Sunday, September 1, 2019 2:29 PM
> To: users@dpdk.org
> Subject: [dpdk-users] How DPDK initialize PCIe DMA engine?
>
> Dear DPDK Community members,
Hi Kevin!
> I am new to DPDK. After reading through the documentation and doing web search
> a couple of days, I am still not clear how DPDK initialize PCIe DMA engine.
>
> As far as I know, the PCIe scan / probe / intialization is pretty
> standardized, but the DMA engines along with the PCIe are very different from
> vendor to vendor.
>
> My question is, what's the best place to implement the DMA initilization code
> within the DPDK framework and how?
>
> Could you give me an example ?
There is a DMA engine driver which has been upstreamed in the 19.08 release,
please see the patchset cover-letter here; http://patches.dpdk.org/cover/55872/
The cover letter gives lots of details, and the 9 patches following it enable
the device itself. Patch 2/9 is the patch that enables a new PCI device to register
as a rawdev, which is probably the best way to enable your device:
http://patches.dpdk.org/patch/55874/
> Best regards.
>
> Thanks,
> Kevin Yuan
Hope that helps, -Harry
prev parent reply other threads:[~2019-09-02 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 13:29 Yuan Kevin
2019-09-02 9:31 ` Van Haaren, Harry [this message]
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=E923DB57A917B54B9182A2E928D00FA6758D967E@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=bruce.richardson@intel.com \
--cc=kevin-yuan@live.com \
--cc=users@dpdk.org \
/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).