From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>, dev@dpdk.org
Cc: stable@dpdk.org, maxime.coquelin@redhat.com
Subject: Re: [dpdk-dev] [PATCH v2 0/6] use IOVAs check based on DMA mask
Date: Tue, 3 Jul 2018 13:33:01 +0100 [thread overview]
Message-ID: <cf7b795b-8871-a979-a40a-1a267018025a@intel.com> (raw)
In-Reply-To: <1530619789-33337-1-git-send-email-alejandro.lucero@netronome.com>
On 03-Jul-18 1:09 PM, Alejandro Lucero wrote:
> This patchset adds, mainly, a check for ensuring IOVAs are within a
> restricted range due to addressing limitations with some devices. There
> are two known cases: NFP and IOMMU VT-d emulation.
>
> With this check IOVAs out of range are detected and PMDs can abort
> initialization. For the VT-d case, IOVA VA mode is allowed as long as
> IOVAs are within the supported range, avoiding to forbid IOVA VA by
> default.
>
> For the addressing limitations known cases, there are just 40(NFP) or
> 39(VT-d) bits for handling IOVAs. When using IOVA PA, those limitations
> imply 1TB(NFP) or 512M(VT-d) as upper limits, which is likely enough for
> most systems. With machines using more memory, the added check will
> ensure IOVAs within the range.
>
> With IOVA VA, and because the way the Linux kernel serves mmap calls
> in 64 bits systems, 39 or 40 bits are not enough. It is possible to
> give an address hint with a lower starting address than the default one
> used by the kernel, and then ensuring the mmap uses that hint or hint plus
> some offset. With 64 bits systems, the process virtual address space is
> large enoguh for doing the hugepages mmaping within the supported range
> when those addressing limitations exist. This patchset also adds a change
> for using such a hint making the use of IOVA VA a more than likely
> possibility when there are those addressing limitations.
>
> The check is not done by default but just when it is required. This
> patchset adds the check for NFP initialization and for setting the IOVA
> mode is an emulated VT-d is detected.
>
> This patchset applies on 17.11.3.
>
> Similar changes will be submitted to main DPDK branch soon.
>
> v2:
> - add get_addr_hint function
> - call munmap when hint given and not used by mmap
> - create dma mask in one step
> - refactor logs
>
>
General comment - new API's should probably be added to the .map files?
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-07-03 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 12:09 Alejandro Lucero
2018-07-03 12:09 ` [dpdk-dev] [PATCH v2 1/6] mem: add function for checking memsegs IOVAs addresses Alejandro Lucero
2018-07-03 12:37 ` Burakov, Anatoly
2018-07-03 12:09 ` [dpdk-dev] [PATCH v2 2/6] ethdev: add function for checking IOVAs by a device Alejandro Lucero
2018-07-03 12:09 ` [dpdk-dev] [PATCH v2 3/6] bus/pci: use IOVAs check when setting IOVA mode Alejandro Lucero
2018-07-03 12:09 ` [dpdk-dev] [PATCH v2 4/6] mem: use address hint for mapping hugepages Alejandro Lucero
2018-07-03 12:37 ` Burakov, Anatoly
2018-07-03 12:09 ` [dpdk-dev] [PATCH v2 5/6] net/nfp: check hugepages IOVAs based on DMA mask Alejandro Lucero
2018-07-03 12:09 ` [dpdk-dev] [PATCH v2 6/6] net/nfp: support IOVA VA mode Alejandro Lucero
2018-07-03 12:33 ` Burakov, Anatoly [this message]
2018-10-05 12:06 [dpdk-dev] [PATCH v2 0/6] use IOVAs check based on DMA mask 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=cf7b795b-8871-a979-a40a-1a267018025a@intel.com \
--to=anatoly.burakov@intel.com \
--cc=alejandro.lucero@netronome.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).