From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: santosh <santosh.shukla@caviumnetworks.com>,
Jianfeng Tan <jianfeng.tan@intel.com>,
dev@dpdk.org, ferruh.yigit@intel.com
Cc: sergio.gonzalez.monroy@intel.com, thomas@monjalon.net,
Peter Xu <peterx@redhat.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] net: enable IOVA mode for PMDs
Date: Fri, 5 Jan 2018 13:57:56 +0100 [thread overview]
Message-ID: <237773b9-0379-40b3-19c1-40c3eb37fe3b@redhat.com> (raw)
In-Reply-To: <4b239748-4b7c-b98d-7123-a5baeb6c8059@caviumnetworks.com>
Hi Santosh
On 01/05/2018 01:10 PM, santosh wrote:
> Hi Maxim,
>
>
> On Friday 05 January 2018 04:02 PM, Maxime Coquelin wrote:
>> Hi Jianfeng,
>>
>> On 10/11/2017 12:33 PM, 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>
>>> ---
>
> [...]
>
>> Ferruh, I see you also faced problems with KNI, how did you solved it?
>>
> By checking lsmod for rte_kni module and if found then set .iova_mode = _pa, refer [1].
> You may follow similar approach.. meaning detect emulation mode Or if not then
> other-way to introduce --iova-mode=<> eal arg.
Thanks for the information
Detecting whether we are in host or guest is not that trivial, and as
Peter pointed me out, the VT-d specifies the 39bits guest address width
so there are certainly some processors in the wild using it.
And I don't think introducing a new EAL arg in -stable is a good idea.
If this is the only solution, then we should keep PA by default.
When using intel IOMMU, I think the best solution is to forbid VA mode
if GAW is 39 bits.
Regards,
Maxime
> [1] http://dpdk.org/browse/dpdk/tree/lib/librte_eal/linuxapp/eal/eal.c#n810
>
> Thanks.
>
>> Thanks,
>> Maxime
>>
>> [0]: https://bugzilla.redhat.com/show_bug.cgi?id=1530957#c3
>
next prev parent reply other threads:[~2018-01-05 12:58 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
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 [this message]
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=237773b9-0379-40b3-19c1-40c3eb37fe3b@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=peterx@redhat.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).