From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev <dev@dpdk.org>,
stable@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [dpdk-stable] [PATCH 3/6] bus/pci: use IOVAs check when setting IOVA mode
Date: Tue, 3 Jul 2018 11:08:08 +0100 [thread overview]
Message-ID: <CAD+H993QToFZ45cuGq1QA3J7HA+1VyU=fdmbg8ZvB2h9y2V19w@mail.gmail.com> (raw)
In-Reply-To: <544f7536-9140-850a-8a01-7b6e15909ae4@intel.com>
On Tue, Jul 3, 2018 at 10:10 AM, Burakov, Anatoly <anatoly.burakov@intel.com
> wrote:
> On 02-Jul-18 6:27 PM, Alejandro Lucero wrote:
>
>> Although VT-d emulation currently only supports 39 bits, it could
>> be iovas being within that supported range. This patch allows
>> IOVA mode in such a case.
>>
>> Indeed, memory initialization code can be modified for using lower
>> virtual addresses than those used by the kernel for 64 bits processes
>> by default, and therefore memsegs iovas can use 39 bits or less for
>> most system. And this is likely 100% true for VMs.
>>
>> Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
>> ---
>>
>
> General question - is this issue only applicable to PCI? Do other buses
> need this?
>
>
I think there could be other buses or devices with those limitations.
Ideally, we could do more things like just discarding those memsegs out of
range, but that would imply other changes.
IMHO, this is good enough and just if it turns out this is causing
problems, other solution should be implemented. But with most current
systems out there, I do not think this is a priority.
> --
> Thanks,
> Anatoly
>
next prev parent reply other threads:[~2018-07-03 10:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 17:26 [dpdk-stable] [PATH 0/6] Use IOVAs check based on DMA mask Alejandro Lucero
2018-07-02 17:26 ` [dpdk-stable] [PATCH 1/6] mem: add function for checking memsegs IOVAs addresses Alejandro Lucero
2018-07-03 9:07 ` Burakov, Anatoly
2018-07-03 10:01 ` Alejandro Lucero
2018-07-02 17:26 ` [dpdk-stable] [PATCH 2/6] ethdev: add function for checking IOVAs by a device Alejandro Lucero
2018-07-02 17:27 ` [dpdk-stable] [PATCH 3/6] bus/pci: use IOVAs check when setting IOVA mode Alejandro Lucero
2018-07-03 9:10 ` Burakov, Anatoly
2018-07-03 10:08 ` Alejandro Lucero [this message]
2018-07-02 17:27 ` [dpdk-stable] [PATCH 4/6] mem: use address hint for mapping hugepages Alejandro Lucero
2018-07-03 9:17 ` Burakov, Anatoly
2018-07-03 10:44 ` Alejandro Lucero
2018-07-03 10:46 ` Burakov, Anatoly
2018-07-02 17:27 ` [dpdk-stable] [PATCH 5/6] net/nfp: check hugepages IOVAs based on DMA mask Alejandro Lucero
2018-07-02 17:27 ` [dpdk-stable] [PATCH 6/6] net/nfp: support IOVA VA mode Alejandro Lucero
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='CAD+H993QToFZ45cuGq1QA3J7HA+1VyU=fdmbg8ZvB2h9y2V19w@mail.gmail.com' \
--to=alejandro.lucero@netronome.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=stable@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).