From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>, dev@dpdk.org
Cc: santosh.shukla@caviumnetworks.com,
sergio.gonzalez.monroy@intel.com, thomas@monjalon.net,
ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH 2/2] net: enable IOVA mode for PMDs
Date: Wed, 11 Oct 2017 18:56:01 +0800 [thread overview]
Message-ID: <6ffd175f-1497-8ff1-f71b-a9d4561846ec@intel.com> (raw)
In-Reply-To: <fcc7babd-3ba4-a66b-3d43-6180056b761a@intel.com>
On 10/11/2017 6:43 PM, Burakov, Anatoly wrote:
> On 11-Oct-17 11:33 AM, Jianfeng Tan wrote:
>> If we want to enable IOVA mode, introduced by
>> commit 93878cf0255e ("eal: introduce helper API for IOVA mode"),
>> we need PMDs (for PCI devices) to expose this flag.
>>
>> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
>> ---
>
> Is this the complete list of drivers which need this flag? Do other
> devices (e.g. cryptodev?) need this flag?
No, these are just NICs from Intel (as an example). If other NICs want
to enable this, I'm more than happy to cover it in v2.
Thanks,
Jianfeng
next prev parent reply other threads:[~2017-10-11 10:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 10:33 [dpdk-dev] [PATCH 0/2] enable 4KB + VFIO-PCI Jianfeng Tan
2017-10-11 10:33 ` [dpdk-dev] [PATCH 1/2] eal: honor IOVA mode for no-huge case Jianfeng Tan
2017-10-11 11:27 ` Burakov, Anatoly
2017-10-11 11:30 ` santosh
2017-10-31 21:49 ` Ferruh Yigit
2017-10-31 22:37 ` Ferruh Yigit
2017-11-01 1:10 ` Ferruh Yigit
2017-10-11 10:33 ` [dpdk-dev] [PATCH 2/2] net: enable IOVA mode for PMDs Jianfeng Tan
2017-10-11 10:43 ` Burakov, Anatoly
2017-10-11 10:56 ` Tan, Jianfeng [this message]
2017-10-11 11:30 ` Burakov, Anatoly
2017-10-11 11:33 ` santosh
2018-01-05 10:32 ` Maxime Coquelin
2018-01-05 12:04 ` Maxime Coquelin
2018-01-05 12:10 ` santosh
2018-01-05 12:57 ` Maxime Coquelin
2017-10-11 10:47 ` [dpdk-dev] [PATCH 0/2] enable 4KB + VFIO-PCI Burakov, Anatoly
2017-10-11 10:50 ` Thomas Monjalon
2017-10-12 19:57 ` Ferruh Yigit
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=6ffd175f-1497-8ff1-f71b-a9d4561846ec@intel.com \
--to=jianfeng.tan@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=santosh.shukla@caviumnetworks.com \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=thomas@monjalon.net \
/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).